pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,397,408
← previous block
next block →
recent activity
Analyzing
Block #91,397,408
11 transactions · 11 stateful · 2026-07-29 16:58:14 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,397,408
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
execOrders
#8
setData
#9
execOrders
#10
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x14eb2f47…8a2e
0x34b655…2a6f
4 touches
1 conflict
0x266a2581…acae
0x34b655…2a6f
4 touches
1 conflict
0x266a2581…acaf
0x34b655…2a6f
4 touches
1 conflict
0xad2bb81f…4d6b
0x34b655…2a6f
4 touches
1 conflict
0xb06ba996…6a69
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
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
0x14eb2f47d3…928a2e
Audit this contract →
← previous block
·
next block →
recent activity