pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,436,764
← previous block
next block →
recent activity
Analyzing
Block #96,436,764
9 transactions · 6 stateful · 2026-08-16 08:01:32 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,436,764
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
#3
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
#6
setData
#7
execOrders
#8
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe283e878…7262
0x34b655…2a6f
4 touches
1 conflict
0xa359130f…4254
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
0x34b655…2a6f
2 touches
0 conflicts
0x39126904…24d8
0x34b655…2a6f
2 touches
0 conflicts
0x5df7cf2b…bbe5
0x34b655…2a6f
2 touches
0 conflicts
0x7a4885a1…e7e4
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
0xe283e878f8…797262
Audit this contract →
← previous block
·
next block →
recent activity