pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,043,103
56 transactions · 37 stateful · 2026-05-07 14:31:24 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #73,043,103 · 56 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1435w1539w1641w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd26973d4…4748
0xd32edf…ff58
35 touches
153 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x7d4f80a4…bb1a
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 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
153 conflicts on slot 0xd26973d4a2…b24748
Audit this contract →
← previous block·next block →recent activity