pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,351,910
52 transactions · 32 stateful · 2026-05-13 15:58:31 UTC
Parallelism
81/100
Blocked
69%
Avg conflicts / tx
1.38
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,351,910 · 52 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w310w422w525w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5ee79db…2b33
0xd32edf…ff58
15 touches
28 conflicts
0x8d47c9a4…f11b
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0019
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0029
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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 0xc5ee79db68…762b33
Audit this contract →
← previous block·next block →recent activity