← previous blocknext block →recent activity
Analyzing
Block #72,817,263
9 transactions · 8 stateful · 2026-05-06 13:27:43 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,817,263 · 9 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
0xb3870dbe…bef3
0x2a68ba…90c5
4 touches
1 conflict
0x589f09b8…31fa
0x065c9d…c394
3 touches
1 conflict
0xf397a32c…a531
0x065c9d…c394
2 touches
1 conflict
0x1203203b…2818
0x065c9d…c394
2 touches
0 conflicts
0x4b214fb0…64ec
0x065c9d…c394
2 touches
0 conflicts
0x80908825…fcfd
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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