pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,918,851
← previous block
next block →
recent activity
Analyzing
Block #85,918,851
11 transactions · 8 stateful · 2026-07-06 06:02:55 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,918,851
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transfer
· blocks 1
#3
0x6a4b4587
#4
0x13389092
#5
executeBatch
#6
0x0f6795d9
#7
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#10
0xc2e37a…9bb8
#2
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeaced15b…2221
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x15bae5fc…9f7e
0x57ea24…2cec
2 touches
0 conflicts
0x3eb250ee…1187
0x57ea24…2cec
2 touches
0 conflicts
0x5c491fdb…3ecc
0x57ea24…2cec
2 touches
0 conflicts
0x611cb8f2…c656
0x57ea24…2cec
2 touches
0 conflicts
0x767df73b…894a
0x57ea24…2cec
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:
USDC (USDC)
1 conflict on slot
0xeaced15b26…bf2221
Audit this contract →
← previous block
·
next block →
recent activity