pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,742,743
← previous block
next block →
recent activity
Analyzing
Block #80,742,743
48 transactions · 12 stateful · 2026-06-12 06:41:10 UTC
Parallelism
94
/100
Blocked
25
%
Avg conflicts / tx
0.06
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,742,743
· 48 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
batchUpdate
#2
0xab083028
· blocks 1
#4
execOrders
#5
execOrders
#6
execOrders
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
execOrders
#18
execOrders
#19
execOrders
#20
execOrders
#21
execOrders
#22
execOrders
#23
execOrders
#24
execOrders
#25
execOrders
#26
execOrders
#27
execOrders
#28
execOrders
#29
execOrders
#30
execOrders
#31
execOrders
#32
execOrders
#33
execOrders
#34
execOrders
#35
execOrders
#36
execOrders
#37
execOrders
#38
execOrders
#39
updateDataFeedsValuesPartial
#40
0x6a2baa7d
· blocks 1
#42
0x3f5c179b
#44
execFwdPositionOps
#45
execFwdPositionOps
#46
setData
#47
execOrders
#3
0xab083028
· blocks 1
#41
0x6a2baa7e
#43
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
40
w0
41
w1
43
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x40c9380a…2115
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x102ca5f5…be7a
0x40c49f…2af0
2 touches
0 conflicts
0x1cfddc31…cecc
0x40c49f…2af0
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
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity