pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,300,334
← previous block
next block →
recent activity
Analyzing
Block #86,300,334
12 transactions · 9 stateful · 2026-07-08 00:29:31 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,300,334
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x57368ddf
#6
batchUpdate
#8
0x4d6428…f840
#9
0x05db60…5ed5
#10
setData
#11
0x39435dac
#3
0x39435dac
· blocks 1
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x3b115d7b…33ac
0x2a68ba…90c5
2 touches
0 conflicts
0x60e67008…f6aa
0x34b655…2a6f
2 touches
0 conflicts
0x831dbc32…b84a
0x34b655…2a6f
2 touches
0 conflicts
0x8cd684d0…c3cb
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
0xec0e022022…becb90
Audit this contract →
← previous block
·
next block →
recent activity