pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,681,641
55 transactions · 34 stateful · 2026-05-10 13:24:44 UTC
Parallelism
73/100
Blocked
71%
Avg conflicts / tx
2.2
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,681,641 · 55 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1040w1144w1245w1346w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34ec0665…6f8a
0xd32edf…ff58
27 touches
91 conflicts
0x00000000…002c
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001c
0x1b6862…e19c
16 touches
28 conflicts
0xd0ec60a1…d244
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 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 0x34ec06650c…fe6f8a
Audit this contract →
← previous block·next block →recent activity