pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,926,042
39 transactions · 36 stateful · 2026-05-11 16:43:10 UTC
Parallelism
64/100
Blocked
81%
Avg conflicts / tx
3.41
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,926,042 · 39 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w59w211w326w627w728w829w931w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x0b0d3b45…a368
0x34b655…2a6f
16 touches
28 conflicts
0xe4f0f159…0c50
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0029
0x1b6862…e19c
12 touches
15 conflicts
0xd0ec60a1…d241
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity