pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,430
38 transactions · 26 stateful · 2026-05-10 11:01:24 UTC
Parallelism
66/100
Blocked
73%
Avg conflicts / tx
2.37
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,660,430 · 38 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w826w927w1028w1137w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b7d87a2…a6dc
0xd32edf…ff58
25 touches
78 conflicts
0x394c3833…b4ab
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002c
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
78 conflicts on slot 0x6b7d87a2f2…05a6dc
Audit this contract →
← previous block·next block →recent activity