pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,425,893
19 transactions · 16 stateful · 2026-05-04 17:59:47 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.37
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,425,893 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w17w08w110w011w112w213w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d7700db…d256
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd4f5d210…6592
0x065c9d…c394
3 touches
1 conflict
0x3555d21c…7d23
0x188d58…ea8e
2 touches
0 conflicts
0x3555d21c…7d24
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
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: 0xd32edf66…9fff58
3 conflicts on slot 0x0d7700db04…e9d256
Audit this contract →
← previous block·next block →recent activity