← previous blocknext block →recent activity
Analyzing
Block #74,442,060
9 transactions · 9 stateful · 2026-05-14 01:58:41 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,442,060 · 9 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
1w02w16w17w2
- 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
0xefd9cd9f…b3f0
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xa6d2bfa3…51b2
0x065c9d…c394
3 touches
1 conflict
0xefdad6a1…a7d2
0x065c9d…c394
3 touches
1 conflict
0xbd0d70ac…baff
0x065c9d…c394
2 touches
0 conflicts
0xcfbaa937…49ca
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