pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#83,480,666
← previous block
next block →
recent activity
Analyzing
Block #83,480,666
10 transactions · 9 stateful · 2026-06-24 23:10:03 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#83,480,666
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xa96df62f
#3
batchCancelOrders
#4
setData
#5
updateTemporalNumericValuesV1
#6
0xe9316489
#7
execOrders
· blocks 1
#9
0xc7e3ec2c
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99ebc4d…22f9
0x34b655…2a6f
4 touches
1 conflict
0x571cb36d…3b3d
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xde1dd4e4…bdbd
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x163a2b4e…07bb
0x96b79e…d00a
2 touches
0 conflicts
0x1347c219…2e22
0xacc0a0…fd62
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
0xe99ebc4d01…5b22f9
Audit this contract →
← previous block
·
next block →
recent activity