pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,597,780
41 transactions · 35 stateful · 2026-05-10 04:01:11 UTC
Parallelism
68/100
Blocked
74%
Avg conflicts / tx
2.24
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,597,780 · 41 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
1w02w13w05w17w08w19w210w311w412w513w017w018w119w225w326w435w236w839w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa91c899f…6ee3
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
12 touches
15 conflicts
0x9db64d13…fb98
0x34b655…2a6f
12 touches
15 conflicts
0xd49762c9…1359
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0xd84e22f4…ccfb
0x34b655…2a6f
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: 0x34b6552d…112a6f
21 conflicts on slot 0xa91c899f02…fa6ee3
Audit this contract →
← previous block·next block →recent activity