pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,233,310
← previous block
next block →
recent activity
Analyzing
Block #100,233,310
16 transactions · 15 stateful · 2026-08-29 16:35:02 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,233,310
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
0xab083028
#4
0x6ad2e98b
#5
execOrders
#6
0x5acec890
#7
0x5acec890
#8
0x928e4afa
#9
setData
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
CreateMemory
#13
CreateMemory
#14
CreateMemory
#15
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x130d8881…3206
0x34b655…2a6f
2 touches
0 conflicts
0x15698ac9…2a46
0x34b655…2a6f
2 touches
0 conflicts
0x1aa85bda…e324
0x34b655…2a6f
2 touches
0 conflicts
0x3c9eb1c3…9acf
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.
← previous block
·
next block →
recent activity