pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,250,140
← previous block
next block →
recent activity
Analyzing
Block #86,250,140
9 transactions · 8 stateful · 2026-07-07 18:54:35 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,250,140
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x39435dac
· blocks 1
#4
redeemDelegations
#5
0xed82b078
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#3
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf195ad96…e0c3
0x34b655…2a6f
4 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
4 touches
1 conflict
0xcb15bf2c…78d1
0x34b655…2a6f
4 touches
1 conflict
0xcf94f773…2dae
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x72b8b170…3237
0x34b655…2a6f
2 touches
0 conflicts
0xa5d0a730…f1e1
0x57ea24…2cec
2 touches
0 conflicts
0xbbd96e4f…d11f
0x57ea24…2cec
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
0xf195ad96b6…00e0c3
Audit this contract →
← previous block
·
next block →
recent activity