pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,604,594
← previous block
next block →
recent activity
Analyzing
Block #98,604,594
13 transactions · 13 stateful · 2026-08-23 23:20:38 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,604,594
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#2
matchOrders
#4
exactInputSingle
#5
0x5acec890
#6
execOrders
#7
0x59558d29
#8
execFwdPositionOpsV2
#9
0x3f5c179b
#10
execFwdPositionOpsV2
#11
0x6a8b80be
#12
setData
#3
permit2TransferAndMulticall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0002
0x0c428e…07a4
4 touches
1 conflict
0x00000000…0003
0x0c428e…07a4
4 touches
1 conflict
0x50b4806e…c048
0x3bd359…433a
4 touches
1 conflict
0x20b50479…b75c
0x0158ab…1a70
4 touches
1 conflict
0x00000000…0000
0x5357bf…ab9f
2 touches
0 conflicts
0x00000000…0001
0x5357bf…ab9f
2 touches
0 conflicts
0x00000000…0005
0x5357bf…ab9f
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:
0x0c428ed2…0607a4
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity