pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,169,664
← previous block
next block →
recent activity
Analyzing
Block #94,169,664
12 transactions · 11 stateful · 2026-08-08 09:27:13 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,169,664
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
updatePosition
#7
batchUpdate
#9
bet
#10
setData
#11
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b32e9b…6b1c
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01df0928…3426
0x34b655…2a6f
2 touches
0 conflicts
0x01df0928…3427
0x34b655…2a6f
2 touches
0 conflicts
0x17c24c5b…471c
0x34b655…2a6f
2 touches
0 conflicts
0x3572f533…4b93
0x34b655…2a6f
2 touches
0 conflicts
0x3620a8f6…8b86
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
0xc0b32e9bdb…9f6b1c
Audit this contract →
← previous block
·
next block →
recent activity