pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,791,946
← previous block
next block →
recent activity
Analyzing
Block #86,791,946
10 transactions · 8 stateful · 2026-07-10 07:16:52 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,791,946
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
removeLiquidityNATIVE
#3
0x0f6795d9
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#7
0x0f6795d9
#8
setData
#9
withdraw
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xdd75d6f7…dc18
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e3
0x34b655…2a6f
4 touches
1 conflict
0x3e690221…c7e4
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x261d4c00…a3f2
0x34b655…2a6f
3 touches
1 conflict
0xc3b4e393…2a34
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity