pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,653,836
48 transactions · 32 stateful · 2026-05-10 10:17:01 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.63
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #73,653,836 · 48 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w09w110w114w015w216w017w118w219w320w421w322w125w230w333w434w535w636w739w840w941w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2f16288…145d
0xd32edf…ff58
21 touches
55 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0x63e48b…53f2
8 touches
6 conflicts
0x00000000…0003
0x63e48b…53f2
8 touches
6 conflicts
0x9a555477…19a8
0x754704…b603
8 touches
6 conflicts
0x00000000…0004
0x63e48b…53f2
8 touches
6 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 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
55 conflicts on slot 0xc2f162888b…ff145d
Audit this contract →
← previous block·next block →recent activity