pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,883,746
← previous block
next block →
recent activity
Analyzing
Block #86,883,746
11 transactions · 10 stateful · 2026-07-10 17:30:47 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,883,746
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4d8dc985
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
forward
#7
0x0f6795d9
· blocks 1
#9
0x6a512cbf
#10
setData
#8
0x0f6795d9
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
0xad15ca0d…a3d5
0x34b655…2a6f
4 touches
1 conflict
0xe2ce91e2…b99e
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x3151b440…d0aa
0x34b655…2a6f
2 touches
0 conflicts
0x49f58aca…82bd
0x34b655…2a6f
2 touches
0 conflicts
0x57330c5d…9973
0x34b655…2a6f
2 touches
0 conflicts
0x6479ca3b…c795
0x34b655…2a6f
2 touches
0 conflicts
0x6f132c01…cdcc
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
0xad15ca0d46…1ea3d5
Audit this contract →
← previous block
·
next block →
recent activity