← previous blocknext block →recent activity
Analyzing
Block #84,748,650
19 transactions · 17 stateful · 2026-06-30 20:03:07 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,748,650 · 19 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w07w111w012w113w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x969f2d28…4fa2
0x0555e3…2b9c
4 touches
1 conflict
0xe92fd8b2…882a
0xd18b7e…414b
4 touches
1 conflict
0x00000000…0002
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0003
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0012
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001a
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001b
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0022
0xd2634e…53b1
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped BTC (WBTC)
1 conflict on slot 0x969f2d28f8…334fa2
Audit this contract →
← previous block·next block →recent activity