pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,485,839
← previous block
next block →
recent activity
Analyzing
Block #86,485,839
11 transactions · 9 stateful · 2026-07-08 21:09:16 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,485,839
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x39435dac
#4
0x0f6795d9
#5
0x0f6795d9
· blocks 1
#6
0x6a4ebcf3
#7
setData
#8
0xa35289…07d0
#9
0xc2fddb…25fc
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x714b3452…483f
0x065c9d…c394
2 touches
0 conflicts
0xdba61307…e074
0x065c9d…c394
2 touches
0 conflicts
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x1546e1b4…1e15
0x34b655…2a6f
2 touches
0 conflicts
0x21d22421…0b7a
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
0x0ab54c30a6…82b88e
Audit this contract →
← previous block
·
next block →
recent activity