pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,559,938
46 transactions · 37 stateful · 2026-04-30 17:46:08 UTC
Parallelism
72/100
Blocked
68%
Avg conflicts / tx
2.54
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,559,938 · 46 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w28w19w013w017w218w119w226w327w428w529w630w331w732w833w935w1036w1145w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f1334c3…82e1
0xd32edf…ff58
25 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x9dce5f78…29c2
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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: 0xd32edf66…9fff58
78 conflicts on slot 0x1f1334c348…0882e1
Audit this contract →
← previous block·next block →recent activity