← previous blocknext block →recent activity
Analyzing
Block #74,287,464
11 transactions · 9 stateful · 2026-05-13 08:49:51 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,287,464 · 11 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
1w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53e3c5d1…6b4c
0x065c9d…c394
3 touches
1 conflict
0x0633faef…6470
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x238d48d1…c5dc
0x065c9d…c394
2 touches
0 conflicts
0x5705ea39…f0f1
0x065c9d…c394
2 touches
0 conflicts
0x585cc3c3…d566
0x065c9d…c394
2 touches
0 conflicts
0xb0ce029d…4859
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 0x53e3c5d136…906b4c
Audit this contract →
← previous block·next block →recent activity