pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,107,286
13 transactions · 10 stateful · 2026-05-17 04:04:22 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,107,286 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w07w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2aad33e…6aab
0x065c9d…c394
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x403c5f85…8a03
0x065c9d…c394
3 touches
1 conflict
0xdfd11f85…865f
0x065c9d…c394
3 touches
1 conflict
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x4cea0b8b…b730
0x065c9d…c394
2 touches
0 conflicts
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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
1 conflict on slot 0xf2aad33e6b…e06aab
Audit this contract →
← previous block·next block →recent activity