pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,679
14 transactions · 13 stateful · 2026-05-04 15:05:05 UTC
Parallelism
71/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,399,679 · 14 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
1w02w13w24w35w06w18w210w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3bd55803…5d4a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x8c3ca31d…df9a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
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: 0x1b68626d…2de19c
6 conflicts on slot 0x3bd558039d…705d4a
Audit this contract →
← previous block·next block →recent activity