pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,460,873
← previous block
next block →
recent activity
Analyzing
Block #84,460,873
39 transactions · 25 stateful · 2026-06-29 12:04:36 UTC
Parallelism
87
/100
Blocked
56
%
Avg conflicts / tx
0.54
Longest chain
5
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#84,460,873
· 39 txs across 5 waves · depth 5
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
wave
w4
#0
syscallReward
#1
0x6a425fcc
· blocks 1
#3
0x6a425fcb
#4
0x6a425fcc
#5
0x6a425fcb
#6
0xc1274a2e
· blocks 2
#7
addLiquidityNATIVE
#10
updateDataFeedsValuesPartial
#11
updateDataFeedsValuesPartial
#12
updatePrices
· blocks 1
#13
updatePrices
#14
updatePrices
#15
updatePrices
#16
updatePrices
#18
updatePrices
#19
updatePrices
#20
updatePrices
#21
execOrders
· blocks 2
#23
0x6a425fcb
#24
0x6a425fcc
#25
0x98717539
· blocks 2
#29
0x62be7533
#30
0x0c7abd22
· blocks 1
#35
setData
#38
0x6a425fcc
#2
0x6a425fcc
#8
0xab083028
· blocks 2
#17
updatePrices
#22
execOrders
· blocks 2
#9
0xab083028
· blocks 1
#26
0x98717539
· blocks 2
#31
0xed82b078
· blocks 2
#36
execOrders
· blocks 1
#27
0x98717539
#28
0x98717539
· blocks 1
#32
0xed82b078
· blocks 1
#37
execOrders
#33
0xed82b078
#34
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
6
w0
8
w1
9
w2
12
w0
17
w1
21
w0
22
w1
25
w0
26
w2
27
w3
28
w3
30
w0
31
w2
32
w3
33
w4
34
w4
36
w2
37
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
6 touches
3 conflicts
0x3dffb05d…2e8b
0x34b655…2a6f
4 touches
1 conflict
0x4af5a706…2fb1
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x8e83fd35…b5d0
0x34b655…2a6f
4 touches
1 conflict
0x91ff239c…e07b
0x34b655…2a6f
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
0xf2f76ab392…f3623e
Audit this contract →
← previous block
·
next block →
recent activity