← previous blocknext block →recent activity
Analyzing
Block #72,311,380
6 transactions · 6 stateful · 2026-05-04 05:16:47 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,311,380 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c8b3a45…9631
0x065c9d…c394
4 touches
1 conflict
0x1e27b3c8…554b
0x065c9d…c394
3 touches
1 conflict
0xf1f274cb…5daa
0x065c9d…c394
3 touches
1 conflict
0x2217c443…7809
0x065c9d…c394
2 touches
0 conflicts
0x824082f4…dd24
0x065c9d…c394
2 touches
0 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
2 touches
0 conflicts
0xf823e97f…2ee6
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity