pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,284,371
50 transactions · 35 stateful · 2026-05-04 02:16:11 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
1.16
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #72,284,371 · 50 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
1w02w13w24w35w46w57w68w415w522w624w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b1e4d5…57dc
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
10 touches
10 conflicts
0xfac61869…a55b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
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
21 conflicts on slot 0x49b1e4d50b…9657dc
Audit this contract →
← previous block·next block →recent activity