pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,456,135
25 transactions · 21 stateful · 2026-05-14 03:32:23 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,456,135 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w29w310w211w315w016w117w218w320w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce2b6650…ecc3
0x5c2513…7777
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x00c46468…f328
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0000
0xcc67aa…c71c
8 touches
6 conflicts
0x44ad89ba…cf83
0x5c2513…7777
8 touches
6 conflicts
0x00000000…0001
0xcc67aa…c71c
8 touches
6 conflicts
0xa2ed1a0b…ba75
0xd32edf…ff58
7 touches
6 conflicts
0xffe431af…8faa
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: 0x5c2513cf…487777
6 conflicts on slot 0xce2b6650f3…b0ecc3
Audit this contract →
← previous block·next block →recent activity