pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,862,425
← previous block
next block →
recent activity
Analyzing
Block #94,862,425
15 transactions · 14 stateful · 2026-08-10 19:47:03 UTC
Parallelism
87
/100
Blocked
7
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,862,425
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updatePrices
#3
execFwdPositionOps
#4
execFwdPositionOps
#5
0x3f5c179b
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
0x6a7a2b2e
#9
setData
· blocks 1
#11
redeemDelegations
#12
execOrders
#13
execOrders
#14
0x59558d29
#10
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x067bd7d7…fa42
0x34b655…2a6f
2 touches
0 conflicts
0x240aec46…0b68
0x34b655…2a6f
2 touches
0 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
2 touches
0 conflicts
0x39d8fc83…042e
0x34b655…2a6f
2 touches
0 conflicts
0x3e3f27ce…580c
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity