pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,763,453
← previous block
next block →
recent activity
Analyzing
Block #85,763,453
11 transactions · 9 stateful · 2026-07-05 12:47:49 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,763,453
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
0x6a4a52ed
#4
execFwdPositionOps
#5
0x3f5c179b
#6
0x3f5c179b
#7
batchUpdate
· blocks 1
#9
0x786b62…81cb
#10
setData
#8
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe471e679…6149
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2b8e668a…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x2decb942…ae9d
0x34b655…2a6f
2 touches
0 conflicts
0x48b13e5e…3c2a
0x34b655…2a6f
2 touches
0 conflicts
0x73784451…3f29
0x34b655…2a6f
2 touches
0 conflicts
0x9365e097…ff56
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xe471e6798d…756149
Audit this contract →
← previous block
·
next block →
recent activity