← previous blocknext block →recent activity
Analyzing
Block #72,317,939
6 transactions · 5 stateful · 2026-05-04 06:00:26 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,317,939 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd77c589…f3c3
0x065c9d…c394
4 touches
1 conflict
0x1cc6bf51…f021
0x065c9d…c394
3 touches
1 conflict
0x9aeef174…65eb
0x065c9d…c394
3 touches
1 conflict
0x34d8966f…23df
0x065c9d…c394
2 touches
0 conflicts
0x99c17569…c417
0x065c9d…c394
2 touches
0 conflicts
0xcccabc14…cbe4
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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 0xfd77c589c4…9ef3c3
Audit this contract →
← previous block·next block →recent activity