pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,918,907
22 transactions · 18 stateful · 2026-05-11 15:55:41 UTC
Parallelism
50/100
Blocked
61%
Avg conflicts / tx
2.55
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,918,907 · 22 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
5w06w17w28w39w410w511w612w713w814w915w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
22 touches
55 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
16 touches
28 conflicts
0x4f483049…3cc7
0x34b655…2a6f
16 touches
28 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
16 touches
28 conflicts
0xac8e97a0…8426
0x34b655…2a6f
16 touches
28 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
14 touches
21 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
55 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity