pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,136,550
← previous block
next block →
recent activity
Analyzing
Block #96,136,550
13 transactions · 10 stateful · 2026-08-15 06:51:37 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,136,550
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xdf921160
· blocks 1
#2
0xcf7468f4
#3
updatePrices
#4
execOrders
#5
0x5acec890
#6
0x5acec890
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#10
setData
#11
0xb5592e…59a0
#12
0x61d59c2d
#9
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b219c89…9b78
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1eced4db…6e94
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x9ff176a9ad…67152e
Audit this contract →
← previous block
·
next block →
recent activity