← previous blocknext block →recent activity
Analyzing
Block #74,622,986
15 transactions · 12 stateful · 2026-05-14 22:10:32 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,622,986 · 15 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
1w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x12333566…fc17
0x065c9d…c394
2 touches
0 conflicts
0x29092c3a…a20b
0x065c9d…c394
2 touches
0 conflicts
0x8f928f69…2f2a
0x065c9d…c394
2 touches
0 conflicts
0x9a477162…edf5
0x065c9d…c394
2 touches
0 conflicts
0xe0e33513…1cab
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