pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,891,665
← previous block
next block →
recent activity
Analyzing
Block #90,891,665
10 transactions · 9 stateful · 2026-07-27 22:32:02 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,891,665
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
executeBatch
#3
placeAndExecuteMarketSell
· blocks 1
#5
execFwdPositionOps
#6
execFwdPositionOps
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
placeAndExecuteMarketSell
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x69e79a93…ea9d
0x851145…3f07
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x32363a87…c2cc
0xe52b14…7230
2 touches
0 conflicts
0x32363a87…c2ce
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
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
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity