pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,539,863
← previous block
next block →
recent activity
Analyzing
Block #93,539,863
13 transactions · 12 stateful · 2026-08-06 04:37:58 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,539,863
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
execFwdPositionOps
#8
placeAndExecuteMarketBuy
#9
forward
#10
transfer
· blocks 1
#12
setData
#2
matchOrders
#11
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x4b39e22c…60e5
0x754704…b603
4 touches
1 conflict
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x303ace4f…eae8
0x754704…b603
4 touches
1 conflict
0x03fccbac…059f
0x34b655…2a6f
2 touches
0 conflicts
0xc2a783bf…25e3
0x34b655…2a6f
2 touches
0 conflicts
0xca841faa…486a
0x34b655…2a6f
2 touches
0 conflicts
0xd71000d2…271f
0x34b655…2a6f
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:
USDC (USDC)
1 conflict on slot
0x42041feca2…afbd86
Audit this contract →
← previous block
·
next block →
recent activity