pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,632,603
28 transactions · 26 stateful · 2026-05-14 23:14:40 UTC
Parallelism
32/100
Blocked
69%
Avg conflicts / tx
6.11
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #74,632,603 · 28 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1618w1719w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea8e0098…9798
0xa7283d…0ace
38 touches
171 conflicts
0x536e2740…61ac
0x3bd359…433a
38 touches
171 conflicts
0xa472d565…9fe4
0x3bd359…433a
38 touches
171 conflicts
0x8fa7a69c…8fd7
0x7be9bb…7777
38 touches
171 conflicts
0x00000000…0002
0xa7283d…0ace
38 touches
171 conflicts
0xea8e0098…9795
0xa7283d…0ace
38 touches
171 conflicts
0xea8e0098…9796
0xa7283d…0ace
38 touches
171 conflicts
0xea8e0098…9797
0xa7283d…0ace
38 touches
171 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
171 conflicts on slot 0xea8e009864…5d9798
Audit this contract →
← previous block·next block →recent activity