pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,555,199
← previous block
next block →
recent activity
Analyzing
Block #96,555,199
11 transactions · 9 stateful · 2026-08-16 17:57:31 UTC
Parallelism
82
/100
Blocked
44
%
Avg conflicts / tx
0.36
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,555,199
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#3
execOrder
· blocks 2
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#2
execOrders
#4
execOrder
#5
execOrder
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xb18e1e9d…2705
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x6100f5dd…6a7f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc87e767e…4bba
0x34b655…2a6f
4 touches
1 conflict
0xe21234e7…bded
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xafb8e71eb0…ec9285
Audit this contract →
← previous block
·
next block →
recent activity