← previous blocknext block →recent activity
Analyzing
Block #71,037,930
19 transactions · 16 stateful · 2026-04-28 07:45:20 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #71,037,930 · 19 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
1w02w16w07w18w29w010w112w214w316w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa02838a3…bc54
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
6 touches
3 conflicts
0xe5c0ee9b…c29b
0x34b655…2a6f
6 touches
3 conflicts
0xf3808e5a…dbfb
0x34b655…2a6f
6 touches
3 conflicts
0xa92c8763…6d7f
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 0xa02838a385…ffbc54
Audit this contract →
← previous block·next block →recent activity