pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,167,507
← previous block
next block →
recent activity
Analyzing
Block #86,167,507
11 transactions · 10 stateful · 2026-07-07 09:42:42 UTC
Parallelism
73
/100
Blocked
30
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,167,507
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
· blocks 1
#3
execFwdPositionOps
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6a4cca89
#6
startRound
#7
setData
#10
execOrders
#2
updatePrices
#8
execOrders
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0xf357ed8b…e65c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x8501273e…45a7
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
2 touches
0 conflicts
0x5dd1f5d4…deac
0x34b655…2a6f
2 touches
0 conflicts
0x76ac2d54…2cd5
0x34b655…2a6f
2 touches
0 conflicts
0xbbb9fa77…d121
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:
0x04fdeac2…f747d7
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity