pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,014,227
45 transactions · 35 stateful · 2026-05-07 11:19:14 UTC
Parallelism
71/100
Blocked
69%
Avg conflicts / tx
2.4
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,014,227 · 45 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w618w719w826w927w1028w1129w1230w834w736w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa943d6cc…0c3e
0xd32edf…ff58
25 touches
78 conflicts
0xba5743c7…21c6
0x1b6862…e19c
10 touches
10 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0xe6455d1f…1029
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
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
78 conflicts on slot 0xa943d6cce2…b30c3e
Audit this contract →
← previous block·next block →recent activity