pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,201,207
46 transactions · 35 stateful · 2026-05-08 08:03:24 UTC
Parallelism
78/100
Blocked
74%
Avg conflicts / tx
1.85
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,201,207 · 46 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w614w125w733w834w938w239w140w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a383649…b36d
0xd32edf…ff58
19 touches
45 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd53220ed…4736
0x1b6862…e19c
8 touches
6 conflicts
0x8a35acfb…d1ac
0x8d66a4…3095
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
45 conflicts on slot 0x5a383649e4…0ab36d
Audit this contract →
← previous block·next block →recent activity