pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,592,424
← previous block
next block →
recent activity
Analyzing
Block #96,592,424
9 transactions · 9 stateful · 2026-08-16 21:04:46 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,592,424
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
updateDataFeedsValuesPartial
#3
setData
#4
0x3f5c179b
#5
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x2d94ecd9…43db
0x34b655…2a6f
2 touches
0 conflicts
0x3b5fbc7d…c8fe
0x34b655…2a6f
2 touches
0 conflicts
0x3e403ed4…f52b
0x34b655…2a6f
2 touches
0 conflicts
0x5c88208a…cd3a
0x34b655…2a6f
2 touches
0 conflicts
0x68c07cb9…ae14
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
0x0d488000e2…143831
Audit this contract →
← previous block
·
next block →
recent activity