← previous blocknext block →recent activity
Analyzing
Block #71,064,996
10 transactions · 9 stateful · 2026-04-28 10:45:30 UTC
Parallelism
60/100
Blocked
44%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,064,996 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w26w17w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x131a2e…0da9
6 touches
3 conflicts
0x47b807a2…3307
0x131a2e…0da9
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x4ab14837…e1b2
0x2a68ba…90c5
4 touches
1 conflict
0x44352f23…98d8
0x065c9d…c394
2 touches
0 conflicts
0xc0a6feef…c424
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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