pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,631,397
← previous block
next block →
recent activity
Analyzing
Block #80,631,397
27 transactions · 15 stateful · 2026-06-11 18:18:50 UTC
Parallelism
89
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,631,397
· 27 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
updatePrices
· blocks 2
#5
updatePrices
#7
updatePrices
#8
updatePrices
#9
updatePrices
#10
execOrders
#11
execOrders
#12
0x3f5c179b
#13
claimWithRecipient
#14
0x3f5c179b
#15
execFwdPositionOps
#16
execFwdPositionOps
#17
0x6a2afc82
#18
setData
#19
0xcfa65e…75cc
#20
0xbcef5b…7919
#21
0x2351d9…cd6e
#22
0xe65635…6ae4
#23
0x201d57…e0e8
#24
execOrders
· blocks 1
#26
0xc7e3ec2c
#4
updatePrices
· blocks 1
#25
execOrders
#6
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w2
24
w0
25
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb18bf8…e9f3
6 touches
3 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
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:
0xb18bf8fc…77e9f3
3 conflicts on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity