← previous blocknext block →recent activity
Analyzing
Block #71,647,637
21 transactions · 19 stateful · 2026-05-01 03:29:45 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,647,637 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w37w48w310w411w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0002
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0xac9789f8…28b4
0xd32edf…ff58
7 touches
6 conflicts
0xd77e90ec…8c04
0x3bd359…433a
6 touches
3 conflicts
0x08943ea2…ed03
0x754704…b603
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: 0x63e48b72…8c53f2
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity