pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,638,484
← previous block
next block →
recent activity
Analyzing
Block #96,638,484
9 transactions · 6 stateful · 2026-08-17 00:56:25 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,638,484
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe70e54…1214
#2
0x42e2ee…cb25
#3
0xa96df62f
#4
execOrders
#5
execFwdPositionOpsV2
· blocks 1
#7
updateDataFeedsValuesPartial
#8
setData
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bdb07b7…9d1b
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0f15f74f…8d71
0x34b655…2a6f
2 touches
0 conflicts
0x0f15f74f…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x3767c336…8dae
0x34b655…2a6f
2 touches
0 conflicts
0x39c8eb9b…8782
0x34b655…2a6f
2 touches
0 conflicts
0x3e1b21c6…b1e4
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
0x4bdb07b70b…c39d1b
Audit this contract →
← previous block
·
next block →
recent activity