pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,736,461
← previous block
next block →
recent activity
Analyzing
Block #98,736,461
10 transactions · 10 stateful · 2026-08-24 10:40:25 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,736,461
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0c7abd22
#3
permit2TransferAndMulticall
· blocks 1
#4
0x59558d29
#6
execFwdPositionOpsV2
#7
execFwdPositionOpsV2
#8
setData
#9
execOrders
#5
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad6fe2fc…8fc3
0xd5d960…eaee
4 touches
1 conflict
0x00000000…000b
0xbeef06…b8f5
4 touches
1 conflict
0x00000000…000f
0xbeef06…b8f5
4 touches
1 conflict
0x2b48a867…0578
0xbeef06…b8f5
4 touches
1 conflict
0x65ff8182…f9bb
0xbeef06…b8f5
4 touches
1 conflict
0x9d266cee…2f00
0xbeef06…b8f5
4 touches
1 conflict
0xe5d0a9bf…8d82
0xbeef06…b8f5
4 touches
1 conflict
0x249241e4…1f19
0xd5d960…eaee
4 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:
0xd5d960e8…a1eaee
1 conflict on slot
0xad6fe2fcc5…a58fc3
Audit this contract →
← previous block
·
next block →
recent activity