pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,571,611
← previous block
next block →
recent activity
Analyzing
Block #84,571,611
9 transactions · 8 stateful · 2026-06-30 00:23:44 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,571,611
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execOrders
· blocks 1
#3
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1c3d1764…3842
0x34b655…2a6f
2 touches
0 conflicts
0x24be6934…997d
0x34b655…2a6f
2 touches
0 conflicts
0x2b111712…0e59
0x34b655…2a6f
2 touches
0 conflicts
0x2e0a4136…1b01
0x34b655…2a6f
2 touches
0 conflicts
0x329f2f7d…dcff
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
0x086db8fc6e…830024
Audit this contract →
← previous block
·
next block →
recent activity