pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,741,749
50 transactions · 35 stateful · 2026-05-01 13:56:24 UTC
Parallelism
74/100
Blocked
77%
Avg conflicts / tx
2.88
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #71,741,749 · 50 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
1w02w13w24w35w46w57w68w714w416w535w836w939w1040w1142w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c4fcab7…3169
0xd32edf…ff58
25 touches
78 conflicts
0x00000000…0002
0x7e9d3a…9fda
22 touches
55 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x78694995…f66c
0x1b6862…e19c
8 touches
6 conflicts
0x17606ba6…1b6e
0x754704…b603
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: 0xd32edf66…9fff58
78 conflicts on slot 0x5c4fcab7c7…693169
Audit this contract →
← previous block·next block →recent activity