pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,478,545
← previous block
next block →
recent activity
Analyzing
Block #94,478,545
10 transactions · 9 stateful · 2026-08-09 11:34:41 UTC
Parallelism
80
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,478,545
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5acec890
· blocks 1
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updatePriceFeedsIfNecessary
#9
setData
#3
0x5acec890
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0087ca84…0b18
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0xa8a56a8f…3924
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x5bb548a1…d9d5
0x34b655…2a6f
3 touches
1 conflict
0x4e58f1d6…2fca
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
0x0087ca844e…1a0b18
Audit this contract →
← previous block
·
next block →
recent activity