pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,628,078
← previous block
next block →
recent activity
Analyzing
Block #86,628,078
11 transactions · 10 stateful · 2026-07-09 13:01:14 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,628,078
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0xab083028
#5
0x0f6795d9
#6
0x0f6795d9
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#10
0xc7e3ec2c
#2
0x0c7abd22
#4
0x938bf18e
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e80434a…a96d
0x0555e3…2b9c
4 touches
1 conflict
0x00000000…0000
0x2d82ac…5fd8
4 touches
1 conflict
0x00000000…0001
0x2d82ac…5fd8
4 touches
1 conflict
0x38b5b2ce…c5bb
0x2d82ac…5fd8
4 touches
1 conflict
0xf9da5665…2703
0x754704…b603
4 touches
1 conflict
0x7cdb03e6…62d8
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0003
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
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:
Wrapped BTC (WBTC)
1 conflict on slot
0x8e80434a22…09a96d
Audit this contract →
← previous block
·
next block →
recent activity