← previous blocknext block →recent activity
Analyzing
Block #71,043,973
26 transactions · 22 stateful · 2026-04-28 08:25:34 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,043,973 · 26 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
1w02w05w19w214w015w116w217w018w119w220w321w324w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
10 touches
10 conflicts
0xb62dcdfd…43ba
0xd32edf…ff58
7 touches
6 conflicts
0x0520da1d…c88e
0x34b655…2a6f
6 touches
3 conflicts
0x3d6ad949…c225
0x34b655…2a6f
6 touches
3 conflicts
0x414e9446…4b59
0x34b655…2a6f
6 touches
3 conflicts
0x5f02eb78…3afe
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
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 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity