pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,592,824
← previous block
next block →
recent activity
Analyzing
Block #96,592,824
9 transactions · 7 stateful · 2026-08-16 21:06:46 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,592,824
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
updateTemporalNumericValuesV1
#7
setData
#8
execOrders
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05dabb1a…f91e
0x34b655…2a6f
2 touches
0 conflicts
0x0be747d5…22e0
0x34b655…2a6f
2 touches
0 conflicts
0x0be747d5…22e1
0x34b655…2a6f
2 touches
0 conflicts
0x1a4d6370…ed62
0x34b655…2a6f
2 touches
0 conflicts
0x39bd1fab…a39c
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
0x745952b2a0…a6d90c
Audit this contract →
← previous block
·
next block →
recent activity