pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,744,312
71 transactions · 55 stateful · 2026-05-01 14:13:30 UTC
Parallelism
82/100
Blocked
75%
Avg conflicts / tx
2.76
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,744,312 · 71 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w110w214w222w323w124w425w526w647w448w549w650w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x7e9d3a…9fda
26 touches
78 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x7d43649a…c3b6
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x0d622e34…0000
0x681e90…ae09
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0a6cb118…4ca8
0x1b6862…e19c
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: 0x7e9d3a8a…4f9fda
78 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity