One Parquet row per observed transaction with first-seen time, time pending, fee rate, ancestor package fields and an outcome of confirmed, dropped or unresolved, plus tables comparing pending sets across providers and summarising block composition. A collector polls several mempool providers and records each transaction until it confirms or disappears. Useful for fee and confirmation-time modelling; the public release is a sample window and fee fields are often missing.
A CSV with one row per closed Lightning channel: short channel id, capacity, closing timestamp, a reason code separating mutual from forced closes, the closing transaction id, the alias of the owning node and the total on-chain fee in satoshis. The author queried the mempool.space API and added the fees of the transactions sweeping the closing outputs. Useful for costing close types; it covers a few large nodes only.
Lightning Network profile tables as Parquet, one row per node or per channel, with capacity, channel counts, fee policy, funding transaction, feature bits and centrality ranks. Bitcoin Data Labs derives them from Lightning gossip and publishes them with a full graph JSON, summary JSON snapshots and a curated file of node entity and role tags. Useful for ranking and classifying routing nodes; the tags and inferred implementation labels are heuristic.