pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,343,513
51 transactions · 37 stateful · 2026-05-08 23:50:05 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
2.25
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #73,343,513 · 51 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w723w830w931w1050w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8c7a13c5…0516
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x6f08361d…bda6
0x065c9d…c394
10 touches
10 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
10 touches
10 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
10 touches
10 conflicts
0xf537eaa0…73c8
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 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
66 conflicts on slot 0x8c7a13c533…7f0516
Audit this contract →
← previous block·next block →recent activity