pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,661,784
← previous block
next block →
recent activity
Analyzing
Block #83,661,784
9 transactions · 7 stateful · 2026-06-25 19:18:27 UTC
Parallelism
67
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,661,784
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
updateDataFeedsValuesPartial
#4
compound
#5
settlePredictions
#6
setData
#7
0x6a3d7f7b
#3
0x5a5d9a99
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd63138b…63d9
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05402b79…ecb0
0x34b655…2a6f
2 touches
0 conflicts
0x100f5aad…3c51
0x34b655…2a6f
2 touches
0 conflicts
0x3405238a…68b6
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x581b0a83…6303
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
0xcd63138b1f…b763d9
Audit this contract →
← previous block
·
next block →
recent activity