pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,946,995
← previous block
next block →
recent activity
Analyzing
Block #86,946,995
10 transactions · 9 stateful · 2026-07-11 00:33:26 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,946,995
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
updatePrices
#4
0x0f6795d9
· blocks 1
#5
0x0f6795d9
· blocks 1
#6
0x0f6795d9
#8
0x6a518fce
#9
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x78f9dd3b…66e1
0x34b655…2a6f
4 touches
1 conflict
0x829ce949…af94
0x34b655…2a6f
4 touches
1 conflict
0x8c9ad343…573a
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xc2099fec…321d
0x34b655…2a6f
4 touches
1 conflict
0xc7bdbe36…f859
0x34b655…2a6f
4 touches
1 conflict
0xc7bdbe36…f85a
0x34b655…2a6f
4 touches
1 conflict
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
0x78f9dd3bc3…8266e1
Audit this contract →
← previous block
·
next block →
recent activity