pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,995,179
← previous block
next block →
recent activity
Analyzing
Block #85,995,179
23 transactions · 16 stateful · 2026-07-06 14:32:24 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,995,179
· 23 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#2
0x69a4d7…e10c
#3
updatePrices
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#9
0x3f5c179b
#10
0x3f5c179b
· blocks 1
#11
0x3f5c179b
#12
execFwdPositionOps
#16
setData
#17
0x9d714a…2e27
#18
0x2603ce…ece9
#19
0x6c4ddc…624d
#20
0x529583…0eba
#21
execOrders
#22
0xc7e3ec2c
#4
0xccf50a51
· blocks 2
#13
0xed82b078
#14
0xed82b078
· blocks 1
#15
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
10
w0
13
w2
14
w2
15
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xacf15a7c…401d
0x065c9d…c394
5 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x0a80b08f…c6ac
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
2 touches
0 conflicts
0x00000000…0003
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
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: MarginAccount
3 conflicts on slot
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity