pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,777
20 transactions · 14 stateful · 2026-05-04 15:05:44 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,399,777 · 20 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
1w02w13w24w37w08w09w111w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ce8c9c8…22ed
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe4c6b0cb…0a21
0x1b6862…e19c
4 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
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 0x3ce8c9c8b6…db22ed
Audit this contract →
← previous block·next block →recent activity