pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,422,578
31 transactions · 28 stateful · 2026-04-30 02:27:15 UTC
Parallelism
61/100
Blocked
75%
Avg conflicts / tx
2.42
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #71,422,578 · 31 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w37w48w09w110w211w312w418w519w624w527w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0xf853eb8e…4027
0x34b655…2a6f
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
8 touches
6 conflicts
0x0a809ce1…7894
0x34b655…2a6f
8 touches
6 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
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: 0x34b6552d…112a6f
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity