pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,208,386
← previous block
next block →
recent activity
Analyzing
Block #96,208,386
9 transactions · 8 stateful · 2026-08-15 12:52:55 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,208,386
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
#4
0x29eed2d3
#5
execFwdPositionOpsV2
#6
0xb72757…2fa2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f097c3…4baa
0x34b655…2a6f
4 touches
1 conflict
0x120847e2…98c2
0x34b655…2a6f
4 touches
1 conflict
0xd4702f73…926c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe73b93bf…c0e1
0x34b655…2a6f
3 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
2 touches
0 conflicts
0xe6997d36…4f33
0x34b655…2a6f
2 touches
0 conflicts
0xfe65bb7b…12d7
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
0x64f097c322…a64baa
Audit this contract →
← previous block
·
next block →
recent activity