pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,085
65 transactions · 40 stateful · 2026-05-04 02:07:32 UTC
Parallelism
88/100
Blocked
57%
Avg conflicts / tx
1.09
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,283,085 · 65 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w613w222w354w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
16 touches
28 conflicts
0x7cf7efcf…18ba
0xd32edf…ff58
15 touches
28 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
10 touches
10 conflicts
0x2877f440…c2c8
0x34b655…2a6f
10 touches
10 conflicts
0x3254d19b…f714
0x34b655…2a6f
10 touches
10 conflicts
0x414e9446…4b59
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 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 0xadac4a860c…a3c2bc
Audit this contract →
← previous block·next block →recent activity