← previous blocknext block →recent activity
Analyzing
Block #71,069,897
21 transactions · 20 stateful · 2026-04-28 11:18:12 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,069,897 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w17w08w19w217w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x104887dc…9894
0x34b655…2a6f
4 touches
1 conflict
0x11f25e19…8bb1
0x34b655…2a6f
4 touches
1 conflict
0x2233f38c…0d84
0x34b655…2a6f
4 touches
1 conflict
0x23114fac…630a
0x34b655…2a6f
4 touches
1 conflict
0x32454f9f…67d2
0x34b655…2a6f
4 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: Perpl
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity