pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,283,593
← previous block
next block →
recent activity
Analyzing
Block #96,283,593
11 transactions · 9 stateful · 2026-08-15 19:11:11 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,283,593
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0xa96df62f
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
forward
#7
0xd62522e3
#8
execFwdPositionOpsV2
· blocks 1
#10
setData
#9
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xea1b8c07…b969
0x34b655…2a6f
4 touches
1 conflict
0x00000000…000b
0x5075ea…d70f
2 touches
0 conflicts
0x24ab7abd…c665
0x754704…b603
2 touches
0 conflicts
0x5311f864…0984
0x754704…b603
2 touches
0 conflicts
0xe3571442…b338
0x754704…b603
2 touches
0 conflicts
0x811a2c96…9d02
0x928dc8…8207
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
0xf90c6521bf…2dd8f0
Audit this contract →
← previous block
·
next block →
recent activity