pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,137,331
← previous block
next block →
recent activity
Analyzing
Block #86,137,331
27 transactions · 18 stateful · 2026-07-07 06:21:19 UTC
Parallelism
93
/100
Blocked
6
%
Avg conflicts / tx
0.04
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,137,331
· 27 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
· blocks 1
#2
execute
#4
0x6a4c9b57
#5
0xcf7468f4
#6
0x0c7abd22
#7
0x1094dc9f
#8
main_all
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
updatePrices
#12
execOrders
#13
execOrders
#14
swap
#15
0x62be7533
#16
execFwdPositionOps
#17
execFwdPositionOps
#18
0x3f5c179b
#19
0x3f5c179b
#20
batchUpdate
#21
0xed82b078
#22
0xed82b078
#23
setData
#24
execOrders
#25
execOrders
#26
0xc7e3ec2c
#3
0x50a0b275
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09beabbc…065c
0x188d58…ea8e
4 touches
1 conflict
0x0dbf9688…c6cf
0xd18b7e…414b
4 touches
1 conflict
0xe92fd8b2…882a
0xd18b7e…414b
4 touches
1 conflict
0x00000000…0002
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0003
0xd2634e…53b1
4 touches
1 conflict
0x00000000…0012
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001a
0xd2634e…53b1
4 touches
1 conflict
0x00000000…001b
0xd2634e…53b1
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:
Uniswap: PoolManager
1 conflict on slot
0x09beabbc92…45065c
Audit this contract →
← previous block
·
next block →
recent activity