← previous blocknext block →recent activity
Analyzing
Block #71,041,593
34 transactions · 30 stateful · 2026-04-28 08:09:42 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,041,593 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w08w111w012w114w016w017w118w219w020w321w122w423w527w528w631w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcff337cf…244b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x47b807a2…3307
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity