← previous blocknext block →recent activity
Analyzing
Block #72,215,017
9 transactions · 9 stateful · 2026-05-03 18:30:09 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,215,017 · 9 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6b0ba…a273
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5956b874…1fab
0x065c9d…c394
3 touches
1 conflict
0xed5bde4b…498b
0x065c9d…c394
3 touches
1 conflict
0x3610ec01…67b9
0x065c9d…c394
2 touches
0 conflicts
0x8ad5464a…41cf
0x065c9d…c394
2 touches
0 conflicts
0x8ccbe183…4ff2
0x065c9d…c394
2 touches
0 conflicts
0xc744f3e4…e5b1
0x065c9d…c394
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: Market-MON/USDC
1 conflict on slot 0x9ba6b0ba5e…ffa273
Audit this contract →
← previous block·next block →recent activity