pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,057,020
← previous block
next block →
recent activity
Analyzing
Block #100,057,020
10 transactions · 10 stateful · 2026-08-29 01:47:24 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,057,020
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
· blocks 1
#3
updatePrices
#4
0x5acec890
#5
execFwdPositionOpsV2
#6
batchUpdate
#7
resolve
#8
0x6a923aa4
#9
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
0xe9e92bac…00ed
0x754704…b603
4 touches
1 conflict
0x68c08dd2…be14
0x99c7a7…8bf0
4 touches
1 conflict
0xdfac3ce0…6699
0x99c7a7…8bf0
4 touches
1 conflict
0x00532bf5…5711
0x754704…b603
4 touches
1 conflict
0x0eff0903…8165
0x754704…b603
4 touches
1 conflict
0x3243e72f…1f6d
0x34b655…2a6f
2 touches
0 conflicts
0x3b3642d0…3ef0
0x34b655…2a6f
2 touches
0 conflicts
0x45729b6f…f072
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
0xe9e92baccc…5c00ed
Audit this contract →
← previous block
·
next block →
recent activity