← previous blocknext block →recent activity
Analyzing
Block #72,221,002
6 transactions · 5 stateful · 2026-05-03 19:10:22 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,221,002 · 6 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ca7e5d9…3b12
0x065c9d…c394
4 touches
1 conflict
0x80160b33…10e4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa80e79e6…da4e
0x065c9d…c394
3 touches
1 conflict
0xce976adb…69a7
0x065c9d…c394
3 touches
1 conflict
0x1c869a99…93f0
0x065c9d…c394
3 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
2 touches
0 conflicts
0x1a4b4152…0a08
0x8d0464…4402
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 0x1ca7e5d9d0…493b12
Audit this contract →
← previous block·next block →recent activity