pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,429,553
← previous block
next block →
recent activity
Analyzing
Block #84,429,553
13 transactions · 10 stateful · 2026-06-29 08:35:51 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,429,553
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swapWithBackendSignature
· blocks 1
#2
0xab083028
· blocks 1
#3
updatePrices
#5
0xccf50a51
#6
0x5a5d9a99
#7
0x98717539
#8
updateDataFeedsValuesPartial
#9
execFwdPositionOps
#10
setData
#11
0x9b5ae2…afc3
#12
execOrders
#4
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x4644765c…1111
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0000
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0001
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0003
0x04ddf6…7f33
2 touches
0 conflicts
0x00000000…0008
0x04ddf6…7f33
2 touches
0 conflicts
0x1a069146…5c12
0x0a3323…0a3c
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
1 conflict on slot
0x7d42dc8b22…fefdb6
Audit this contract →
← previous block
·
next block →
recent activity