← previous blocknext block →recent activity
Analyzing
Block #72,458,593
8 transactions · 7 stateful · 2026-05-04 21:37:39 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,458,593 · 8 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fb893e6…a352
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3c075f28…fe50
0x065c9d…c394
3 touches
1 conflict
0x194aca97…63e9
0x065c9d…c394
3 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0b6d25a1…2e3b
0x34b655…2a6f
2 touches
0 conflicts
0x2343b4c2…d6bb
0x34b655…2a6f
2 touches
0 conflicts
0x38dee07f…7598
0x34b655…2a6f
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 0x8fb893e631…bba352
Audit this contract →
← previous block·next block →recent activity