← previous blocknext block →recent activity
Analyzing
Block #71,089,680
44 transactions · 32 stateful · 2026-04-28 13:30:03 UTC
Parallelism
80/100
Blocked
59%
Avg conflicts / tx
1.2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #71,089,680 · 44 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w18w011w012w120w021w122w223w327w335w336w438w639w740w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x21d2cdfc…a217
0xd32edf…ff58
9 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
6 touches
3 conflicts
0xe75ce681…ba61
0x188d58…ea8e
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
21 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity