pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,775,703
86 transactions · 62 stateful · 2026-05-15 15:10:14 UTC
Parallelism
88/100
Blocked
66%
Avg conflicts / tx
1.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #74,775,703 · 86 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w111w015w019w020w121w123w224w325w426w127w538w140w142w250w354w455w556w671w772w773w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0x14098ed7…ccdc
0xd32edf…ff58
17 touches
36 conflicts
0x44ad89ba…cf83
0x5c2513…7777
16 touches
28 conflicts
0x00c46468…f328
0x3bd359…433a
16 touches
28 conflicts
0xa472d565…9fe4
0x3bd359…433a
16 touches
28 conflicts
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xce2b6650…ecc3
0x5c2513…7777
16 touches
28 conflicts
0x00000000…0000
0xcc67aa…c71c
16 touches
28 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: 0xab35264b…1cfa38
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity