pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,548
50 transactions · 33 stateful · 2026-05-04 15:04:12 UTC
Parallelism
60/100
Blocked
73%
Avg conflicts / tx
4.04
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #72,399,548 · 50 txs across 20 waves · depth 20
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
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w814w221w423w924w1029w1130w1232w1333w1434w1539w1640w1741w1842w1944w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70db8159…2f44
0xd32edf…ff58
39 touches
190 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x4d42f16e…a6c8
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
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: 0xd32edf66…9fff58
190 conflicts on slot 0x70db8159d7…5d2f44
Audit this contract →
← previous block·next block →recent activity