pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,453,230
← previous block
next block →
recent activity
Analyzing
Block #100,453,230
12 transactions · 11 stateful · 2026-08-30 11:05:21 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
#100,453,230
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
0x59558d29
#4
0x59558d29
#5
execFwdPositionOpsV2
#6
execFwdPositionOpsV2
#7
transferWithAuthorization
· blocks 1
#9
0x6a940ee9
#10
setData
#11
execOrders
#8
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x1e2721…7805
2 touches
0 conflicts
0x0e0c66fe…796f
0x1e2721…7805
2 touches
0 conflicts
0x00532bf5…5711
0x754704…b603
2 touches
0 conflicts
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x63e367c9…b363
0x754704…b603
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
0xd17580f913…78ece1
Audit this contract →
← previous block
·
next block →
recent activity