pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,043,104
53 transactions · 39 stateful · 2026-05-07 14:31:25 UTC
Parallelism
75/100
Blocked
69%
Avg conflicts / tx
2.09
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,043,104 · 53 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
1w02w14w25w36w47w58w69w710w811w919w320w1021w1134w1035w1136w142w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaccc912…88e8
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x7f189cf6…afab
0x065c9d…c394
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xe4c6b0cb…0a26
0x1b6862…e19c
10 touches
10 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 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 0xfaccc9121e…3a88e8
Audit this contract →
← previous block·next block →recent activity