pev.One block, wave by wave
analyticsdocs
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,421,315
60 transactions · 38 stateful · 2026-05-13 23:40:27 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
1.38
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #74,421,315 · 60 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
1w02w13w24w35w46w57w68w733w645w846w947w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67faa5e2…a16e
0xd32edf…ff58
21 touches
55 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…001b
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002b
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0xb6d6d740…e91d
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
55 conflicts on slot 0x67faa5e2b7…e7a16e
Audit this contract →
← previous block·next block →recent activity