← previous blocknext block →recent activity
Analyzing
Block #74,382,762
8 transactions · 7 stateful · 2026-05-13 19:23:53 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,382,762 · 8 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfd4e2ccc…d3e3
0x065c9d…c394
4 touches
1 conflict
0xfb5573ad…1e2e
0x065c9d…c394
3 touches
1 conflict
0x09c97f82…aa04
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x91b52e44…ce36
0x065c9d…c394
2 touches
0 conflicts
0xb12686ca…1d1a
0x065c9d…c394
2 touches
0 conflicts
0xe042c75d…4de7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity