pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,090,120
31 transactions · 27 stateful · 2026-04-28 13:32:59 UTC
Parallelism
84/100
Blocked
59%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,090,120 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w29w313w014w115w116w317w418w020w121w123w224w226w428w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x801a6e57…d85c
0x34b655…2a6f
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x41755291…977f
0x065c9d…c394
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xf2ce7980…4c2c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x75f928fc…0465
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
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: 0x34b6552d…112a6f
10 conflicts on slot 0x801a6e5726…c1d85c
Audit this contract →
← previous block·next block →recent activity