pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,509,540
← previous block
next block →
recent activity
Analyzing
Block #85,509,540
10 transactions · 9 stateful · 2026-07-04 08:35:54 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,509,540
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0x5a5d9a99
#6
execFwdPositionOps
#7
0x3f5c179b
#8
execFwdPositionOps
#9
setData
#2
0xab083028
· blocks 1
#3
0x6ad2e98b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x75240e59…efa7
0x40c49f…2af0
4 touches
1 conflict
0xd692f65b…ba86
0x40c49f…2af0
4 touches
1 conflict
0x213ee207…a151
0x69df8a…6292
4 touches
1 conflict
0x46279ae7…20dd
0x69df8a…6292
4 touches
1 conflict
0x7f4a8466…f2cc
0x69df8a…6292
4 touches
1 conflict
0x53e50026…6d8c
0x69df8a…6292
4 touches
1 conflict
0x6fffa762…dab7
0x40c49f…2af0
4 touches
1 conflict
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: MarginAccount
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity