pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,201,449
46 transactions · 39 stateful · 2026-05-08 08:05:01 UTC
Parallelism
76/100
Blocked
67%
Avg conflicts / tx
1.96
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,201,449 · 46 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w17w08w19w310w111w016w118w019w120w221w322w423w524w632w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
22 touches
55 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x09a09683…7679
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x91220b8f…7a03
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: 0xab35264b…1cfa38
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity