pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,923,818
← previous block
next block →
recent activity
Analyzing
Block #86,923,818
9 transactions · 9 stateful · 2026-07-10 21:58:37 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,923,818
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
execFwdPositionOps
#7
execFwdPositionOps
#8
setData
#6
execOrders
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
0x65e795ca…0320
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x54f7f60f…43cc
0x34b655…2a6f
2 touches
0 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
2 touches
0 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
2 touches
0 conflicts
0xb543d97e…cc3f
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
0x65e795ca62…450320
Audit this contract →
← previous block
·
next block →
recent activity