pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,796,710
← previous block
next block →
recent activity
Analyzing
Block #86,796,710
11 transactions · 10 stateful · 2026-07-10 07:48:41 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,796,710
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
0x5a5d9a99
#4
0x5a5d9a99
· blocks 1
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x57368ddf
#9
setData
#10
0x34adcf…349c
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb39cb1d8…effa
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x07d8b1e8…78c6
0x34b655…2a6f
2 touches
0 conflicts
0x3e10f4bc…90b6
0x34b655…2a6f
2 touches
0 conflicts
0x447c249a…b42c
0x34b655…2a6f
2 touches
0 conflicts
0x47be1402…75f4
0x34b655…2a6f
2 touches
0 conflicts
0x58123a85…6f7d
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
0xb39cb1d8c6…28effa
Audit this contract →
← previous block
·
next block →
recent activity