pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,599,138
19 transactions · 14 stateful · 2026-05-19 10:57:23 UTC
Parallelism
68/100
Blocked
57%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,599,138 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ba6538a…6eb1
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0000
0x659bd0…a9da
4 touches
1 conflict
0x00000000…0002
0x659bd0…a9da
4 touches
1 conflict
0xcce2fd99…a8eb
0x3bd359…433a
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0xb2f5fe64…bf86
0x065c9d…c394
3 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
15 conflicts on slot 0x5ba6538a2c…e56eb1
Audit this contract →
← previous block·next block →recent activity