pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,597,663
43 transactions · 29 stateful · 2026-05-10 04:00:24 UTC
Parallelism
60/100
Blocked
72%
Avg conflicts / tx
3.33
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,597,663 · 43 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
1w02w13w24w35w46w57w68w79w811w912w1013w1114w1227w1328w1433w1534w1636w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf646c95…0ffb
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0xba5743c7…21c1
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 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
136 conflicts on slot 0xaf646c95a4…320ffb
Audit this contract →
← previous block·next block →recent activity