pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,858
14 transactions · 11 stateful · 2026-05-04 15:06:16 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,399,858 · 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
5w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x56c2c376…0207
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x23e11a62…5906
0x065c9d…c394
2 touches
0 conflicts
0x64cb5b58…2d25
0x065c9d…c394
2 touches
0 conflicts
0x912d3740…d136
0x065c9d…c394
2 touches
0 conflicts
0xb0084534…b41a
0x065c9d…c394
2 touches
0 conflicts
0xcbbd29e3…0c1a
0x065c9d…c394
2 touches
0 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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity