pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,808,498
55 transactions · 39 stateful · 2026-05-11 03:40:11 UTC
Parallelism
80/100
Blocked
79%
Avg conflicts / tx
2.18
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,808,498 · 55 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
1w02w13w24w35w46w511w112w319w420w534w639w746w647w748w849w950w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x126f27cb…ee2a
0xd32edf…ff58
21 touches
55 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0xba5743c7…21c6
0x1b6862…e19c
14 touches
21 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
55 conflicts on slot 0x126f27cbc3…eaee2a
Audit this contract →
← previous block·next block →recent activity