pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,498,556
67 transactions · 55 stateful · 2026-05-05 02:03:39 UTC
Parallelism
84/100
Blocked
67%
Avg conflicts / tx
1.88
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #72,498,556 · 67 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w07w08w111w113w016w219w320w421w531w132w142w243w344w446w547w248w654w355w457w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x7e9d3a…9fda
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8d8c11f7…9d99
0xd32edf…ff58
13 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0xf3981be5…2c47
0x34b655…2a6f
10 touches
10 conflicts
0x6423fcab…a7c1
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity