pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,655,068
← previous block
next block →
recent activity
Analyzing
Block #95,655,068
11 transactions · 9 stateful · 2026-08-13 14:28:18 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,655,068
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xb2d4797b
· blocks 2
#4
0xeb282f7f
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
exactInputSingle
#8
execFwdPositionOps
#9
execFwdPositionOps
#10
setData
#2
0xb2d4797b
· blocks 1
#3
0xb2d4797b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0xa3d97490…c39c
0x1efe02…37d6
2 touches
0 conflicts
0xcf15b62b…532f
0x1efe02…37d6
2 touches
0 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
2 touches
0 conflicts
0x68faa0b9…14af
0x98dc6e…8633
2 touches
0 conflicts
0x5509a4d2…106a
0xea1b8e…c5ec
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:
0x59df8637…6d2780
3 conflicts on slot
0x0000000000…000031
Audit this contract →
← previous block
·
next block →
recent activity