pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,173
44 transactions · 34 stateful · 2026-05-04 02:08:07 UTC
Parallelism
77/100
Blocked
71%
Avg conflicts / tx
1.41
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,283,173 · 44 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w012w118w620w734w835w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x920cb67c…f3a8
0xd32edf…ff58
13 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xbad68552…e6bf
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb1
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: 0xd32edf66…9fff58
21 conflicts on slot 0x920cb67cbe…eef3a8
Audit this contract →
← previous block·next block →recent activity