pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,126,259
← previous block
next block →
recent activity
Analyzing
Block #96,126,259
11 transactions · 10 stateful · 2026-08-15 05:59:49 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,126,259
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x325dd70c
· blocks 1
#3
postPriceList
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
#6
0x3f5c179b
#7
execFwdPositionOpsV2
#8
transfer
#9
setData
#10
0x61d59c2d
#2
0xd60faa87
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x834d94…8555
4 touches
1 conflict
0x00000000…0002
0x834d94…8555
4 touches
1 conflict
0x00000000…0004
0x834d94…8555
4 touches
1 conflict
0x0ef74796…cd18
0x0a3323…0a3c
4 touches
1 conflict
0xa060b594…669d
0x754704…b603
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x3904724e…9a80
0x754704…b603
2 touches
0 conflicts
0x66c70a3f…1e9c
0x754704…b603
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:
0x834d94a0…2e8555
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity