pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,420,884
63 transactions · 37 stateful · 2026-05-13 23:37:35 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
2.43
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,420,884 · 63 txs across 17 waves · depth 17
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
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w710w814w915w1016w1117w1218w1350w1452w1553w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc88e33e…46bf
0xd32edf…ff58
33 touches
136 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x35801c67…bcc1
0x1b6862…e19c
8 touches
6 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
136 conflicts on slot 0xcc88e33e0b…0146bf
Audit this contract →
← previous block·next block →recent activity