pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,307,595
← previous block
next block →
recent activity
Analyzing
Block #86,307,595
11 transactions · 10 stateful · 2026-07-08 01:18:04 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,307,595
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xa96df62f
#3
0x39435dac
· blocks 2
#5
executeBatch
#6
0x9e76c652
#8
updateDataFeedsValuesPartial
#9
setData
#10
0x39435dac
#4
0x39435dac
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9430a4d7…1f35
0x34b655…2a6f
4 touches
1 conflict
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0xacd1b162…bee6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd45e7a3b…85f7
0x34b655…2a6f
2 touches
0 conflicts
0xec0e0220…cb90
0x34b655…2a6f
2 touches
0 conflicts
0x09a15b10…2639
0x754704…b603
2 touches
0 conflicts
0x5149ba0e…d954
0x754704…b603
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
0x9430a4d7e6…111f35
Audit this contract →
← previous block
·
next block →
recent activity