pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,298,372
← previous block
next block →
recent activity
Analyzing
Block #86,298,372
9 transactions · 7 stateful · 2026-07-08 00:16:28 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,298,372
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x39435dac
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x6a4d9754
#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
0xe4a37d08…ffec
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x4c619b7d…f4fa
0x34b655…2a6f
4 touches
1 conflict
0x943b8531…5cd6
0x34b655…2a6f
4 touches
1 conflict
0xb03ccb40…ede4
0x34b655…2a6f
4 touches
1 conflict
0xcfe06a18…b5b5
0x69df8a…6292
2 touches
0 conflicts
0xd8fd2add…50fc
0x69df8a…6292
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
0xe4a37d0813…00ffec
Audit this contract →
← previous block
·
next block →
recent activity