pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,859,949
50 transactions · 33 stateful · 2026-05-06 18:12:23 UTC
Parallelism
76/100
Blocked
70%
Avg conflicts / tx
1.92
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,859,949 · 50 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w014w015w016w118w221w123w224w125w232w333w434w535w636w737w838w939w1040w241w246w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa50e649d…450d
0xd32edf…ff58
23 touches
66 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001c
0x1b6862…e19c
12 touches
15 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x251861eb…78fd
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
6 touches
3 conflicts
0x3c35979a…975d
0x34b655…2a6f
6 touches
3 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
66 conflicts on slot 0xa50e649d4c…3f450d
Audit this contract →
← previous block·next block →recent activity