pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,804,960
40 transactions · 34 stateful · 2026-05-11 03:16:37 UTC
Parallelism
57/100
Blocked
74%
Avg conflicts / tx
3
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,804,960 · 40 txs across 17 waves · depth 17
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
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w110w014w115w216w317w418w519w420w521w622w723w824w632w935w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x157b6348…8604
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xafd59af5…5257
0xc8689a…ee79
10 touches
10 conflicts
0x2484cc15…5afc
0x34b655…2a6f
10 touches
10 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
10 touches
10 conflicts
0x664bf99e…0a8c
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity