pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,649,592
44 transactions · 37 stateful · 2026-05-10 09:48:28 UTC
Parallelism
64/100
Blocked
76%
Avg conflicts / tx
3.32
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #73,649,592 · 44 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w117w119w228w1330w1435w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa1ead81c…e7fe
0xd32edf…ff58
31 touches
120 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
8 touches
6 conflicts
0x15d039e7…4bb6
0x34b655…2a6f
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
6 touches
3 conflicts
0xb159af88…a9e7
0x065c9d…c394
4 touches
1 conflict
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
120 conflicts on slot 0xa1ead81cb6…55e7fe
Audit this contract →
← previous block·next block →recent activity