pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,043,159
46 transactions · 37 stateful · 2026-05-07 14:31:47 UTC
Parallelism
63/100
Blocked
68%
Avg conflicts / tx
3.04
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,043,159 · 46 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1332w1437w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9046ef4f…8943
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
12 touches
15 conflicts
0x580c6fe7…0fe9
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
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
120 conflicts on slot 0x9046ef4f16…678943
Audit this contract →
← previous block·next block →recent activity