pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,475,301
← previous block
next block →
recent activity
Analyzing
Block #93,475,301
9 transactions · 8 stateful · 2026-08-05 23:13:25 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,475,301
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
placeAndExecuteMarketBuy
#6
execFwdPositionOps
#7
handleOps
#8
setData
#2
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f03e539…f4cc
0x754704…b603
4 touches
1 conflict
0xe50f87d9…047c
0x754704…b603
4 touches
1 conflict
0x04413a2a…4bf0
0x99c7a7…8bf0
4 touches
1 conflict
0x6d8bf82a…3f56
0x99c7a7…8bf0
4 touches
1 conflict
0x7aa512ae…d2e0
0x754704…b603
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
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
0x7f03e53912…eef4cc
Audit this contract →
← previous block
·
next block →
recent activity