← previous blocknext block →recent activity
Analyzing
Block #71,283,829
17 transactions · 15 stateful · 2026-04-29 11:02:22 UTC
Parallelism
76/100
Blocked
47%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,283,829 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w111w213w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x408e66bb…3d6b
0x34b655…2a6f
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x9a8fe44f…09c6
0xd32edf…ff58
7 touches
6 conflicts
0x3e0f56fb…e78f
0x34b655…2a6f
6 touches
3 conflicts
0xea2d3331…6e35
0x1b6862…e19c
6 touches
3 conflicts
0xd2252746…4c96
0x34b655…2a6f
6 touches
3 conflicts
0xf06c2cf5…61bd
0x34b655…2a6f
6 touches
3 conflicts
0x5639618d…6388
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 0x408e66bba7…d43d6b
Audit this contract →
← previous block·next block →recent activity