← previous blocknext block →recent activity
Analyzing
Block #72,971,381
16 transactions · 13 stateful · 2026-05-07 06:34:01 UTC
Parallelism
81/100
Blocked
23%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,971,381 · 16 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
3w07w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0x121fa300…5555
0x065c9d…c394
4 touches
1 conflict
0xd5d08ab9…e53d
0x065c9d…c394
3 touches
1 conflict
0xabf92725…20af
0x065c9d…c394
3 touches
1 conflict
0x9921e19b…63c3
0x065c9d…c394
3 touches
1 conflict
0x1a4b4152…0a08
0x6ca43f…c331
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity