pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,366,362
← previous block
next block →
recent activity
Analyzing
Block #99,366,362
14 transactions · 10 stateful · 2026-08-26 15:36:48 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,366,362
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
0x59558d29
#4
0x000000b2
#5
execFwdPositionOpsV2
· blocks 1
#6
0x3f5c179b
#8
0xed82b078
#9
redeemDelegations
#10
transfer
#11
setData
#12
0x000000b2
#13
jMMeC
#7
redeemDelegations
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfca8addf…4b41
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x05086df1…bd5a
0x34b655…2a6f
2 touches
0 conflicts
0x079bf666…56c4
0x34b655…2a6f
2 touches
0 conflicts
0x0c89047a…fccf
0x34b655…2a6f
2 touches
0 conflicts
0x168cce20…53ee
0x34b655…2a6f
2 touches
0 conflicts
0x1760201b…3b6a
0x34b655…2a6f
2 touches
0 conflicts
0x232b0b19…d946
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:
Perpl
1 conflict on slot
0xfca8addf56…094b41
Audit this contract →
← previous block
·
next block →
recent activity