← previous blocknext block →recent activity
Analyzing
Block #71,069,925
19 transactions · 16 stateful · 2026-04-28 11:18:23 UTC
Parallelism
63/100
Blocked
44%
Avg conflicts / tx
0.89
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #71,069,925 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w19w210w315w216w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf853eb8e…4027
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1af
0x8d66a4…3095
6 touches
3 conflicts
0xac8e97a0…8426
0x34b655…2a6f
6 touches
3 conflicts
0x1c913164…5c2e
0x34b655…2a6f
6 touches
3 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
6 touches
3 conflicts
0x49f231bb…c1c2
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 0xf853eb8e72…d84027
Audit this contract →
← previous block·next block →recent activity