pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,300,679
← previous block
next block →
recent activity
Analyzing
Block #86,300,679
12 transactions · 10 stateful · 2026-07-08 00:31:49 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,300,679
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#5
batchUpdate
#6
0xed82b078
#7
setData
#8
execOrders
#9
execOrders
#10
0x5d2fd812
#11
0xc7e3ec2c
#2
execOrders
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0a6f5e37…6c3c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
2 touches
0 conflicts
0x087ba8bb…f0f3
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94e9
0x34b655…2a6f
2 touches
0 conflicts
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity