pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,281,180
← previous block
next block →
recent activity
Analyzing
Block #96,281,180
8 transactions · 7 stateful · 2026-08-15 18:59:03 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,281,180
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#4
0x222d4ad6
#6
setData
#7
flashSwap
#5
execFwdPositionOpsV2
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
0x5655f5c3…6b75
0x34b655…2a6f
4 touches
1 conflict
0x60d732ff…3b8a
0x34b655…2a6f
4 touches
1 conflict
0xa5811d93…8c73
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d71
0x34b655…2a6f
2 touches
0 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x1d8ed744…8aeb
0x34b655…2a6f
2 touches
0 conflicts
0x2c8f52ce…fe9a
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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
0x5655f5c3b4…dd6b75
Audit this contract →
← previous block
·
next block →
recent activity