pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,479,178
53 transactions · 33 stateful · 2026-05-18 21:29:36 UTC
Parallelism
72/100
Blocked
73%
Avg conflicts / tx
2.74
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #75,479,178 · 53 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w610w711w812w913w1015w518w623w724w830w933w1134w1238w1339w1449w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x794de834…9d12
0xd32edf…ff58
29 touches
105 conflicts
0x00000000…0028
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0018
0x1b6862…e19c
14 touches
21 conflicts
0xba5743c7…21bf
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 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
105 conflicts on slot 0x794de834cb…209d12
Audit this contract →
← previous block·next block →recent activity