pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,096,428
← previous block
next block →
recent activity
Analyzing
Block #100,096,428
11 transactions · 11 stateful · 2026-08-29 05:05:48 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,096,428
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
matchOrders
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x59558d29
#6
setData
#7
execFwdPositionOpsV2
#8
bet
#9
execFwdPositionOpsV2
#10
0x6a926924
#3
matchOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53e67340…60f7
0x754704…b603
4 touches
1 conflict
0xf00d2133…d68e
0x754704…b603
4 touches
1 conflict
0x48961b46…3dad
0x99c7a7…8bf0
4 touches
1 conflict
0xa1ac5a56…17d8
0x99c7a7…8bf0
4 touches
1 conflict
0x49f39582…ccc7
0x754704…b603
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
0x53e6734022…4a60f7
Audit this contract →
← previous block
·
next block →
recent activity