pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,648,061
18 transactions · 12 stateful · 2026-05-01 03:32:33 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,648,061 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w310w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05fee3aa…afd6
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x3bd55803…5d4b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0xce8bbe33…b72e
0x3bd359…433a
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
6 conflicts on slot 0x05fee3aa5a…6fafd6
Audit this contract →
← previous block·next block →recent activity