pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,249,975
← previous block
next block →
recent activity
Analyzing
Block #85,249,975
9 transactions · 6 stateful · 2026-07-03 03:47:24 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,249,975
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x0c7abd22
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execOrders
· blocks 1
#6
0x5a5d9a99
#8
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f2c756…0ffc
0x34b655…2a6f
4 touches
1 conflict
0xac912471…5317
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x056ec16c…55b9
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x315e07b8…9823
0x34b655…2a6f
2 touches
0 conflicts
0x3b572e17…2daf
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:
Perpl
1 conflict on slot
0x27f2c75698…900ffc
Audit this contract →
← previous block
·
next block →
recent activity