← previous blocknext block →recent activity
Analyzing
Block #70,845,580
9 transactions · 8 stateful · 2026-04-27 10:24:30 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #70,845,580 · 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08fc3429…16d4
0x065c9d…c394
6 touches
3 conflicts
0x4a27b231…434d
0x065c9d…c394
6 touches
3 conflicts
0xafb9463d…0bae
0x065c9d…c394
6 touches
3 conflicts
0xdb0e25f0…f13e
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0004
0xd0f8a6…badc
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
2 touches
0 conflicts
0xac808a27…82db
0x34b655…2a6f
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 0x08fc342941…4d16d4
Audit this contract →
← previous block·next block →recent activity