pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,042,055
65 transactions · 51 stateful · 2026-05-07 14:24:25 UTC
Parallelism
78/100
Blocked
76%
Avg conflicts / tx
3.05
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,042,055 · 65 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w812w919w921w1023w1149w950w1051w1152w1264w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcfb3c08c…4667
0xd32edf…ff58
27 touches
91 conflicts
0x00000000…0002
0xab3526…fa38
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x394c3833…b4ae
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
12 touches
15 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
91 conflicts on slot 0xcfb3c08c7a…374667
Audit this contract →
← previous block·next block →recent activity