pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,297,384
← previous block
next block →
recent activity
Analyzing
Block #95,297,384
10 transactions · 9 stateful · 2026-08-12 08:24:51 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,297,384
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
closeBetting
#9
setData
#5
execFwdPositionOps
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
0xb2056985…093e
0x34b655…2a6f
4 touches
1 conflict
0xeac03412…4aea
0x34b655…2a6f
4 touches
1 conflict
0xf690a694…03f3
0x34b655…2a6f
4 touches
1 conflict
0xb2056985…093f
0x34b655…2a6f
4 touches
1 conflict
0xcdf1ff19…9963
0x34b655…2a6f
3 touches
1 conflict
0x59a54ff4…d21b
0x34b655…2a6f
2 touches
0 conflicts
0x5aa29d18…83c7
0x34b655…2a6f
2 touches
0 conflicts
0x7c709217…21b4
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
0xb205698556…ac093e
Audit this contract →
← previous block
·
next block →
recent activity