pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,515,956
42 transactions · 28 stateful · 2026-05-14 10:11:36 UTC
Parallelism
74/100
Blocked
82%
Avg conflicts / tx
1.83
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,515,956 · 42 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w58w610w711w812w913w1021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f6da2bf…737d
0xd32edf…ff58
21 touches
55 conflicts
0xfa324e43…8899
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…001d
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002d
0x1b6862…e19c
16 touches
28 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
55 conflicts on slot 0x5f6da2bf8c…f2737d
Audit this contract →
← previous block·next block →recent activity