← previous blocknext block →recent activity
Analyzing
Block #71,070,927
8 transactions · 8 stateful · 2026-04-28 11:25:05 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #71,070,927 · 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x02b0967f…ec09
0x065c9d…c394
4 touches
1 conflict
0xbc14485a…1b0c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x3ab850c1…93c9
0x065c9d…c394
2 touches
1 conflict
0x3ab850c1…93c8
0x065c9d…c394
2 touches
1 conflict
0x8a15ae5c…2286
0x065c9d…c394
2 touches
1 conflict
0x8a15ae5c…2285
0x065c9d…c394
2 touches
1 conflict
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