pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,351,872
49 transactions · 35 stateful · 2026-05-13 15:58:16 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
1.49
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,351,872 · 49 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w010w111w212w013w114w216w322w023w124w225w326w427w528w629w730w837w444w546w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x35fc37cb…7034
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x801a6e57…d85c
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
6 touches
3 conflicts
0x99f080dc…58c1
0x34b655…2a6f
6 touches
3 conflicts
0x9d22c394…c125
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity