pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,492,358
46 transactions · 37 stateful · 2026-05-09 16:20:35 UTC
Parallelism
70/100
Blocked
65%
Avg conflicts / tx
2.07
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,492,358 · 46 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w08w113w114w115w216w017w118w219w320w421w522w027w028w129w230w331w437w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x868859b9…3db5
0x34b655…2a6f
12 touches
15 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
10 touches
10 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
10 touches
10 conflicts
0x55b6a001…1e7a
0x34b655…2a6f
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: 0x34b6552d…112a6f
28 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity