pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,961,545
← previous block
next block →
recent activity
Analyzing
Block #86,961,545
12 transactions · 10 stateful · 2026-07-11 02:10:40 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,961,545
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
0xa96df62f
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#7
0x3f5c179b
#8
0x0f6795d9
#9
0x6a51a698
#10
setData
#11
0xc7e3ec2c
#6
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6696401…27d2
0xd32edf…ff58
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xa059778a…e5f4
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0007
0x067abd…3ea3
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0xa3c36de0…3cf3
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:
FastLane: FastLaneAuctionHandler
1 conflict on slot
0xe6696401a1…7927d2
Audit this contract →
← previous block
·
next block →
recent activity