pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,035,639
37 transactions · 30 stateful · 2026-05-07 13:41:43 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
1.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,035,639 · 37 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w621w722w124w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00236f1f…c16f
0xd32edf…ff58
17 touches
36 conflicts
0xdaca243a…f9de
0x34b655…2a6f
6 touches
3 conflicts
0x0520da1d…c88e
0x34b655…2a6f
4 touches
1 conflict
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3702b140…97ea
0x34b655…2a6f
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
4 touches
1 conflict
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
36 conflicts on slot 0x00236f1f78…c5c16f
Audit this contract →
← previous block·next block →recent activity