pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,616,690
← previous block
next block →
recent activity
Analyzing
Block #99,616,690
9 transactions · 9 stateful · 2026-08-27 12:43:18 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,616,690
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
0x928e4afa
#5
0x59558d29
#6
redeemDelegations
· blocks 1
#8
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8e222e6…f193
0x34b655…2a6f
4 touches
1 conflict
0x3df0422c…fd38
0x34b655…2a6f
4 touches
1 conflict
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd9c216f4…3fd6
0x34b655…2a6f
3 touches
1 conflict
0x0c78ade3…f11a
0x34b655…2a6f
3 touches
1 conflict
0x888134f9…cb10
0x34b655…2a6f
3 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:
Perpl
1 conflict on slot
0xd8e222e6f6…e1f193
Audit this contract →
← previous block
·
next block →
recent activity