pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,826,695
← previous block
next block →
recent activity
Analyzing
Block #80,826,695
53 transactions · 14 stateful · 2026-06-12 16:00:58 UTC
Parallelism
94
/100
Blocked
21
%
Avg conflicts / tx
0.06
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,826,695
· 53 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xed82b078
· blocks 1
#3
0xed82b078
#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
execOrders
#40
execOrders
#41
execOrders
#42
execOrders
#43
updateDataFeedsValuesPartial
#44
updateDataFeedsValuesPartial
#45
execFwdPositionOps
· blocks 1
#46
execFwdPositionOps
#48
execFwdPositionOps
#49
0x3f5c179b
#50
0x3f5c179b
#51
setData
#4
0xed82b078
#47
execFwdPositionOps
· blocks 1
#52
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
45
w0
47
w1
52
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001b
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002b
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c2
0x1b6862…e19c
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:
Perpl
1 conflict on slot
0x0672e4a279…2f8d1f
Audit this contract →
← previous block
·
next block →
recent activity