pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,920,986
25 transactions · 22 stateful · 2026-05-11 16:09:30 UTC
Parallelism
48/100
Blocked
73%
Avg conflicts / tx
2.56
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,920,986 · 25 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
3w04w15w06w17w28w39w410w511w612w713w814w922w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
20 touches
45 conflicts
0xc50e4c77…cc13
0x34b655…2a6f
20 touches
45 conflicts
0xee230b20…5a0f
0x34b655…2a6f
20 touches
45 conflicts
0x9be2b99a…a959
0x34b655…2a6f
18 touches
36 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
18 touches
36 conflicts
0xac8e97a0…8426
0x34b655…2a6f
18 touches
36 conflicts
0x4f483049…3cc7
0x34b655…2a6f
18 touches
36 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
18 touches
36 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