← previous blocknext block →recent activity
Analyzing
Block #71,094,323
21 transactions · 17 stateful · 2026-04-28 14:00:58 UTC
Parallelism
76/100
Blocked
53%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,094,323 · 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
2w03w15w06w17w28w313w014w115w216w318w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c49c85c…ee96
0x34b655…2a6f
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x32454f9f…67d2
0x34b655…2a6f
6 touches
3 conflicts
0x3702b140…97ea
0x34b655…2a6f
6 touches
3 conflicts
0x3e1f7818…2fc8
0x34b655…2a6f
6 touches
3 conflicts
0x4e01a6b9…ed8e
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
6 conflicts on slot 0x8c49c85c3e…afee96
Audit this contract →
← previous block·next block →recent activity