pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,761,187
55 transactions · 35 stateful · 2026-05-15 13:32:58 UTC
Parallelism
85/100
Blocked
54%
Avg conflicts / tx
0.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,761,187 · 55 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w06w017w319w021w322w224w425w526w636w137w238w339w440w542w646w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3fd858de…dcad
0xd32edf…ff58
13 touches
21 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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
21 conflicts on slot 0x3fd858de59…dbdcad
Audit this contract →
← previous block·next block →recent activity