pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,512,845
56 transactions · 43 stateful · 2026-05-19 01:20:36 UTC
Parallelism
75/100
Blocked
72%
Avg conflicts / tx
2.61
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #75,512,845 · 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
1w04w05w17w19w012w115w216w117w219w220w221w322w430w131w332w433w534w635w736w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x2bb9348b…73ea
0xd32edf…ff58
15 touches
28 conflicts
0x9d34b099…ff86
0x34b655…2a6f
14 touches
21 conflicts
0x15698ac9…2a46
0x34b655…2a6f
12 touches
15 conflicts
0x99a21305…dffc
0x2a68ba…90c5
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
10 touches
10 conflicts
0xcb45d9d6…cb81
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: 0x34b6552d…112a6f
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity