pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,683,609
13 transactions · 11 stateful · 2026-05-01 07:29:13 UTC
Parallelism
69/100
Blocked
36%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #71,683,609 · 13 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
1w02w13w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78e81d3d…82d0
0x065c9d…c394
7 touches
6 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0x3ebea2a4…9673
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x6183442f…da15
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0e188149…2faf
0xd32edf…ff58
3 touches
1 conflict
0x679f8359…659f
0x065c9d…c394
3 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: 0x065c9d28…a9c394
6 conflicts on slot 0x78e81d3d2b…2982d0
Audit this contract →
← previous block·next block →recent activity