pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,471,407
50 transactions · 26 stateful · 2026-05-14 05:13:56 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.04
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,471,407 · 50 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w19w217w018w128w129w030w131w232w333w434w036w137w238w341w443w544w646w747w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x592f837c…6a08
0xd32edf…ff58
17 touches
36 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
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
36 conflicts on slot 0x592f837c58…1c6a08
Audit this contract →
← previous block·next block →recent activity