pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,658,329
← previous block
next block →
recent activity
Analyzing
Block #101,658,329
12 transactions · 11 stateful · 2026-09-03 16:08:44 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,658,329
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a999c04
#2
updatePrices
· blocks 1
#4
execOrder
· blocks 1
#5
0x59558d29
#6
redeemDelegations
#7
updatePriceFeedsIfNecessary
#9
0x6a999c04
#10
setData
#11
execOrders
#3
updatePrices
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdc90bed5…58a9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0x0a4008a8…27da
0x1c8a33…d316
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0008
0x98a45d…206a
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:
0xf5b5f7f8…a36d70
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity