← previous blocknext block →recent activity
Analyzing
Block #72,311,234
13 transactions · 11 stateful · 2026-05-04 05:15:48 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,311,234 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf823e97f…2ee6
0x065c9d…c394
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc4a72fb…372a
0x065c9d…c394
3 touches
1 conflict
0x50702f5a…7177
0x065c9d…c394
3 touches
1 conflict
0x34c72c1c…401e
0x065c9d…c394
3 touches
1 conflict
0x00000000…0004
0x559007…1a58
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
3 conflicts on slot 0xf823e97fa0…262ee6
Audit this contract →
← previous block·next block →recent activity