pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,446,030
← previous block
next block →
recent activity
Analyzing
Block #93,446,030
9 transactions · 8 stateful · 2026-08-05 20:46:16 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,446,030
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
approve
#5
0x3f5c179b
#6
execFwdPositionOps
#7
0x6a73a190
#8
execOrders
#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
0xe96cbc90…be66
0x754704…b603
4 touches
1 conflict
0x0d528651…72f0
0x754704…b603
4 touches
1 conflict
0xcf3f3349…b858
0x754704…b603
4 touches
1 conflict
0x6676e87f…b88f
0x2a68ba…90c5
2 touches
0 conflicts
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x447d2e…e9f5
2 touches
0 conflicts
0x2506f9b1…6e68
0x447d2e…e9f5
2 touches
0 conflicts
0x37cbfd73…3abc
0x447d2e…e9f5
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
0xe96cbc90aa…eebe66
Audit this contract →
← previous block
·
next block →
recent activity