← previous blocknext block →recent activity
Analyzing
Block #72,301,734
12 transactions · 8 stateful · 2026-05-04 04:12:31 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,301,734 · 12 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7586ef22…e86b
0x065c9d…c394
4 touches
1 conflict
0x114f5baf…6d8b
0x065c9d…c394
3 touches
1 conflict
0x1f42d7dd…20c2
0x065c9d…c394
2 touches
0 conflicts
0x7dfb59eb…9148
0x065c9d…c394
2 touches
0 conflicts
0xb0bfe9e1…2b0c
0x065c9d…c394
2 touches
0 conflicts
0xbdb4b7ee…cb4a
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