pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,454,419
56 transactions · 47 stateful · 2026-05-14 03:20:54 UTC
Parallelism
75/100
Blocked
74%
Avg conflicts / tx
2.89
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,454,419 · 56 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
1w02w13w24w35w46w57w68w79w810w911w1016w219w923w1024w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d343b40…1dc2
0xd32edf…ff58
21 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…002b
0x1b6862…e19c
12 touches
15 conflicts
0x3bd55803…5d4b
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
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: 0xd32edf66…9fff58
55 conflicts on slot 0x2d343b40d7…6c1dc2
Audit this contract →
← previous block·next block →recent activity