pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,124,939
← previous block
next block →
recent activity
Analyzing
Block #96,124,939
9 transactions · 8 stateful · 2026-08-15 05:53:10 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,124,939
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#5
0x3f5c179b
#6
execFwdPositionOpsV2
#8
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05286dbb…4517
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5b
0x34b655…2a6f
4 touches
1 conflict
0xf4db760d…fc5c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x7d07e5f7…6703
0x34b655…2a6f
2 touches
0 conflicts
0x9fbc6a76…9c29
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
0x05286dbb6e…3d4517
Audit this contract →
← previous block
·
next block →
recent activity