pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,456,460
← previous block
next block →
recent activity
Analyzing
Block #93,456,460
9 transactions · 9 stateful · 2026-08-05 21:38:42 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,456,460
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
0x3f5c179b
#7
0x6a73adda
#8
0x59558d29
#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
0x7aa512ae…d2e0
0x754704…b603
4 touches
1 conflict
0x04413a2a…4bf0
0x99c7a7…8bf0
4 touches
1 conflict
0x6d8bf82a…3f56
0x99c7a7…8bf0
4 touches
1 conflict
0x0641a88f…ffd4
0x34b655…2a6f
2 touches
0 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x7f03e53912…eef4cc
Audit this contract →
← previous block
·
next block →
recent activity