← previous blocknext block →recent activity
Analyzing
Block #74,667,086
12 transactions · 9 stateful · 2026-05-15 03:04:51 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,667,086 · 12 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2c76df4a…1131
0x065c9d…c394
2 touches
0 conflicts
0x3cdea1fa…d9e8
0x065c9d…c394
2 touches
0 conflicts
0xb1d4f2a1…7c58
0x065c9d…c394
2 touches
0 conflicts
0xa6ff25f6…6fef
0x188d58…ea8e
2 touches
0 conflicts
0xa6ff25f6…6ff0
0x188d58…ea8e
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