pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,296,688
60 transactions · 46 stateful · 2026-05-04 03:38:54 UTC
Parallelism
77/100
Blocked
74%
Avg conflicts / tx
2.5
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #72,296,688 · 60 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w111w112w213w119w321w722w832w840w941w1042w1143w1258w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6367e89…5fcf
0xd32edf…ff58
27 touches
91 conflicts
0x24968e6d…0132
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xbb1747e2…f78b
0x34b655…2a6f
10 touches
10 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
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: 0xd32edf66…9fff58
91 conflicts on slot 0xc6367e8904…835fcf
Audit this contract →
← previous block·next block →recent activity