pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,856,136
65 transactions · 46 stateful · 2026-05-06 17:47:01 UTC
Parallelism
80/100
Blocked
70%
Avg conflicts / tx
1.88
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #72,856,136 · 65 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
1w02w13w24w35w413w617w321w447w748w849w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0x2b511cf9…525d
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
10 touches
10 conflicts
0x78e3ec57…8bf9
0x34b655…2a6f
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity