pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,540,489
← previous block
next block →
recent activity
Analyzing
Block #93,540,489
12 transactions · 11 stateful · 2026-08-06 04:41:07 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,540,489
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x3f5c179b
#6
execFwdPositionOps
#7
0x6a7410db
#8
transfer
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#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
0x0e854949…baa7
0x754704…b603
4 touches
1 conflict
0x303ace4f…eae8
0x754704…b603
4 touches
1 conflict
0x4b39e22c…60e5
0x754704…b603
4 touches
1 conflict
0x9ed41050…1125
0x99c7a7…8bf0
4 touches
1 conflict
0xffc3de0b…e501
0x99c7a7…8bf0
4 touches
1 conflict
0x088adada…2aa2
0x34b655…2a6f
2 touches
0 conflicts
0x20b39169…550e
0x34b655…2a6f
2 touches
0 conflicts
0x793b6cb1…63c7
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
0x0e85494967…b0baa7
Audit this contract →
← previous block
·
next block →
recent activity