pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,233,900
← previous block
next block →
recent activity
Analyzing
Block #100,233,900
18 transactions · 17 stateful · 2026-08-29 16:38:00 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,900
· 18 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6ad2e98b
#2
0x928e4afa
#3
execPerpOps
#4
execPerpOps
#5
executeBatch
#6
setData
#7
execFwdPositionOpsV2
#8
updatePosition
#9
0x0c7abd22
#10
transfer
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#15
execOrders
#16
execOrders
#17
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
0x00f19757…9252
0x34b655…2a6f
2 touches
0 conflicts
0x063de7a7…b761
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
0x34b655…2a6f
2 touches
0 conflicts
0x4a5956ef…e226
0x34b655…2a6f
2 touches
0 conflicts
0x5ee1769f…2d59
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