pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,920,403
105 transactions · 75 stateful · 2026-05-16 07:15:29 UTC
Parallelism
82/100
Blocked
80%
Avg conflicts / tx
3.41
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,920,403 · 105 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w69w726w832w933w1072w773w880w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
34 touches
136 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
26 touches
78 conflicts
0x1841718d…21ca
0xd32edf…ff58
19 touches
45 conflicts
0xb9868b52…c77f
0x34b655…2a6f
16 touches
28 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x9885a25f…292b
0x1b6862…e19c
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: 0xab35264b…1cfa38
136 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity