pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,599
85 transactions · 65 stateful · 2026-05-10 11:02:34 UTC
Parallelism
81/100
Blocked
83%
Avg conflicts / tx
2.91
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,660,599 · 85 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w818w822w939w1084w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
22 touches
55 conflicts
0x17606ba6…1b6e
0x754704…b603
18 touches
36 conflicts
0x2c81910e…e2e0
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002c
0x1b6862…e19c
16 touches
28 conflicts
0xc13fac9b…d2d2
0x1b6862…e19c
16 touches
28 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