← previous blocknext block →recent activity
Analyzing
Block #72,861,202
11 transactions · 9 stateful · 2026-05-06 18:20:45 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,861,202 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x4ecad9ad…d22f
0x065c9d…c394
3 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0xb4d80b0e…9e61
0x065c9d…c394
2 touches
0 conflicts
0xd7abca8c…a3be
0x065c9d…c394
2 touches
0 conflicts
0x70b2f813…783c
0x2a68ba…90c5
2 touches
0 conflicts
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
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity