pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,525,720
← previous block
next block →
recent activity
Analyzing
Block #96,525,720
12 transactions · 10 stateful · 2026-08-16 15:29:16 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,525,720
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xcbbdb31a
#3
execPerpOps
#4
execPerpOps
#5
execOrders
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOpsV2
· blocks 1
#10
0x94defb17
#11
setData
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f63d67…5ba0
0x34b655…2a6f
4 touches
1 conflict
0xd7e4217d…7c6b
0x34b655…2a6f
4 touches
1 conflict
0xcd93b2d2…30e6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x742c8909…ac72
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
0x60f63d6751…de5ba0
Audit this contract →
← previous block
·
next block →
recent activity