← previous blocknext block →recent activity
Analyzing
Block #74,440,830
11 transactions · 9 stateful · 2026-05-14 01:50:27 UTC
Parallelism
73/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,440,830 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0x7a8f3d95…6e1f
0x065c9d…c394
3 touches
1 conflict
0x204d1f42…280e
0x065c9d…c394
2 touches
0 conflicts
0x34315aed…ba63
0x065c9d…c394
2 touches
0 conflicts
0x38ea16a2…3f3d
0x065c9d…c394
2 touches
0 conflicts
0x518100e6…64e8
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
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