pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,353,679
← previous block
next block →
recent activity
Analyzing
Block #86,353,679
11 transactions · 11 stateful · 2026-07-08 06:25:52 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,353,679
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
signIn
#3
execFwdPositionOps
· blocks 1
#4
batchUpdate
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a4dede7
#8
setData
#9
approve
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8b18ba0…f380
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1a499b19…cbc6
0x065c9d…c394
2 touches
0 conflicts
0x301c1687…1858
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x88c57a99…9978
0x065c9d…c394
2 touches
0 conflicts
0x9764a88b…163f
0x065c9d…c394
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
0xa8b18ba0f2…07f380
Audit this contract →
← previous block
·
next block →
recent activity