pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,501,735
← previous block
next block →
recent activity
Analyzing
Block #86,501,735
10 transactions · 7 stateful · 2026-07-08 22:55:20 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,501,735
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
#5
0x0f6795d9
#6
setData
#7
0x5e2aff…359b
#8
0x4b35b1…c8a3
#9
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c42d66…97d3
0x34b655…2a6f
4 touches
1 conflict
0xfefb0189…f726
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xaeb5864c…7679
0x2a68ba…90c5
2 touches
0 conflicts
0x0e174308…3f0b
0x34b655…2a6f
2 touches
0 conflicts
0x66230448…7463
0x34b655…2a6f
2 touches
0 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
2 touches
0 conflicts
0x7c6a17fa…e95d
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
0x99c42d6675…d397d3
Audit this contract →
← previous block
·
next block →
recent activity