pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,298,066
← previous block
next block →
recent activity
Analyzing
Block #86,298,066
10 transactions · 8 stateful · 2026-07-08 00:14:25 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,298,066
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x39435dac
· blocks 1
#5
0x0f6795d9
#6
0x3f5c179b
#7
0x57368ddf
#8
setData
#9
0x39435dac
#4
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0xb03ccb40…ede4
0x34b655…2a6f
4 touches
1 conflict
0xbf66c076…62fb
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x0a6eadd4…b990
0x34b655…2a6f
2 touches
0 conflicts
0x151a39c9…e8e2
0x34b655…2a6f
2 touches
0 conflicts
0x170f3b5b…db60
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
0x1d9867ade5…7b6d9a
Audit this contract →
← previous block
·
next block →
recent activity