pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,564,130
← previous block
next block →
recent activity
Analyzing
Block #93,564,130
12 transactions · 10 stateful · 2026-08-06 06:39:57 UTC
Parallelism
83
/100
Blocked
20
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,564,130
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
executePacked
· blocks 1
#2
matchOrders
#3
execPerpOps
#4
0x5acec890
#5
0x5acec890
#7
repayWithCollateral
#8
execFwdPositionOps
· blocks 1
#10
updateDataFeedsValuesPartial
#11
setData
#6
placeAndExecuteMarketSell
#9
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc1aa38d0…a9f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf18f7c3c…f7cc
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x453805…c7fd
2 touches
0 conflicts
0x00000000…000c
0x453805…c7fd
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
0x0778475bb2…63bd75
Audit this contract →
← previous block
·
next block →
recent activity