pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,341
49 transactions · 40 stateful · 2026-05-10 11:00:49 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.51
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,660,341 · 49 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
1w02w13w24w27w08w310w211w213w331w332w437w438w539w640w441w742w843w944w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x38524fae…9deb
0x34b655…2a6f
10 touches
10 conflicts
0xb159af88…a9e7
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x39d8121e…842d
0xd32edf…ff58
9 touches
10 conflicts
0x7f81fb82…633e
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
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: 0x065c9d28…a9c394
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity