pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,837,356
← previous block
next block →
recent activity
Analyzing
Block #75,837,356
10 transactions · 8 stateful · 2026-05-20 13:25:44 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,837,356
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
dagSwapByOrderId
· blocks 2
#4
updateDataFeedsValuesPartial
#5
artefact_keep
#6
withdraw
#7
multicall
#8
0x366fe5db
#9
setData
#2
dagSwapByOrderId
· blocks 1
#3
dagSwapByOrderId
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa2056a0b…a4fd
0x188d58…ea8e
6 touches
3 conflicts
0xd06cc746…27e4
0x384275…7777
6 touches
3 conflicts
0xa2056a0b…a4fc
0x188d58…ea8e
6 touches
3 conflicts
0x3f135308…d203
0x000000…8ba3
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0xb4a84c40…d777
0x000000…012a
2 touches
0 conflicts
0x62e20208…be65
0x0555e3…2b9c
2 touches
0 conflicts
0xa24d15eb…cc92
0x0555e3…2b9c
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:
Uniswap: PoolManager
3 conflicts on slot
0xa2056a0bbc…bba4fd
Audit this contract →
← previous block
·
next block →
recent activity