pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,366,357
47 transactions · 35 stateful · 2026-05-04 11:22:58 UTC
Parallelism
74/100
Blocked
74%
Avg conflicts / tx
1.91
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #72,366,357 · 47 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w18w09w110w318w419w530w531w632w746w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39ff18e4…5483
0xd32edf…ff58
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0x39ff18e494…815483
Audit this contract →
← previous block·next block →recent activity