← previous blocknext block →recent activity
Analyzing
Block #71,041,633
28 transactions · 25 stateful · 2026-04-28 08:09:58 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,041,633 · 28 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
1w02w06w17w08w19w210w313w115w218w319w021w122w424w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x35b65947…44d1
0xc8689a…ee79
6 touches
3 conflicts
0xf3808e5a…dbfb
0x34b655…2a6f
6 touches
3 conflicts
0x65e795ca…0320
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity