pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,915,107
55 transactions · 40 stateful · 2026-05-16 06:40:05 UTC
Parallelism
76/100
Blocked
73%
Avg conflicts / tx
2.27
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #74,915,107 · 55 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w37w48w59w611w716w632w839w940w1041w1142w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb398e123…3819
0xd32edf…ff58
25 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd8d828a7…b64d
0x1b6862…e19c
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: 0xd32edf66…9fff58
78 conflicts on slot 0xb398e12360…e73819
Audit this contract →
← previous block·next block →recent activity