pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,233,094
← previous block
next block →
recent activity
Analyzing
Block #100,233,094
13 transactions · 13 stateful · 2026-08-29 16:33:57 UTC
Parallelism
85
/100
Blocked
15
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,233,094
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
withdraw
· blocks 1
#7
setData
#8
updatePriceFeedsIfNecessary
#9
0x29eed2d3
#10
execFwdPositionOpsV2
#11
commit
#12
execOrders
#2
0x0c7abd22
#6
withdraw
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0036
0x35a73b…6042
4 touches
1 conflict
0xaf831072…51d6
0x69a5f9…2fef
4 touches
1 conflict
0xaf831072…51dc
0x69a5f9…2fef
4 touches
1 conflict
0x2ef1d89b…196d
0x754704…b603
4 touches
1 conflict
0xfda39b6f…d4cc
0x754704…b603
4 touches
1 conflict
0xaf831072…51d5
0x69a5f9…2fef
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
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:
0x35a73bac…1d6042
1 conflict on slot
0x0000000000…000036
Audit this contract →
← previous block
·
next block →
recent activity