pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,648,091
31 transactions · 17 stateful · 2026-05-01 03:32:45 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #71,648,091 · 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
1w02w13w24w36w48w09w412w120w428w029w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe861d200…9549
0xd32edf…ff58
9 touches
10 conflicts
0xce8bbe33…b72e
0x3bd359…433a
8 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
8 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
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: 0xd32edf66…9fff58
10 conflicts on slot 0xe861d20040…619549
Audit this contract →
← previous block·next block →recent activity