← previous blocknext block →recent activity
Analyzing
Block #82,173,540
22 transactions · 18 stateful · 2026-06-18 21:37:29 UTC
Parallelism
82/100
Blocked
28%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,173,540 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w28w19w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x66c5e348…51d0
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1b3114cd…5e2d
0xa6afd3…d132
4 touches
1 conflict
0xa1257a8e…b4ba
0xa6afd3…d132
3 touches
1 conflict
0x2f45fbd2…cee9
0xa6afd3…d132
3 touches
1 conflict
0x6a172125…e22b
0xa6afd3…d132
3 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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity