pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,607,856
25 transactions · 24 stateful · 2026-05-14 20:29:46 UTC
Parallelism
28/100
Blocked
75%
Avg conflicts / tx
6.16
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #74,607,856 · 25 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1618w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcba59bf3…8d20
0xa7283d…0ace
36 touches
153 conflicts
0x536e2740…61ac
0x3bd359…433a
36 touches
153 conflicts
0xa472d565…9fe4
0x3bd359…433a
36 touches
153 conflicts
0x8fa7a69c…8fd7
0x17a62e…7777
36 touches
153 conflicts
0x00000000…0002
0xa7283d…0ace
36 touches
153 conflicts
0xcba59bf3…8d1d
0xa7283d…0ace
36 touches
153 conflicts
0xcba59bf3…8d1e
0xa7283d…0ace
36 touches
153 conflicts
0xcba59bf3…8d1f
0xa7283d…0ace
36 touches
153 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: 0xa7283d07…f90ace
153 conflicts on slot 0xcba59bf334…fa8d20
Audit this contract →
← previous block·next block →recent activity