pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,384
45 transactions · 35 stateful · 2026-05-04 02:09:33 UTC
Parallelism
78/100
Blocked
69%
Avg conflicts / tx
1.87
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #72,283,384 · 45 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
1w02w14w05w06w110w011w115w219w020w121w222w323w424w525w626w727w828w932w333w134w236w338w439w240w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xbad68552…e6bf
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x005fb969…2d97
0x34b655…2a6f
8 touches
6 conflicts
0x17e2d2a0…359e
0x34b655…2a6f
8 touches
6 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
8 touches
6 conflicts
0x2877f440…c2c8
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
45 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity