pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,555,260
← previous block
next block →
recent activity
Analyzing
Block #106,555,260
14 transactions · 11 stateful · 2026-09-20 20:11:37 UTC
Parallelism
93
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,555,260
· 14 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
0x928e4afa
#3
0x0c7abd22
#4
0xab083028
#5
0x5acec890
#6
0xa96df62f
#7
0x59558d29
#8
execPerpOps
#9
execPerpOps
#10
setData
#11
execFwdPositionOpsV2
#12
execFwdPositionOpsV2
#13
0x61d59c2d
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
0x05b1b07a…7a99
0x34b655…2a6f
2 touches
0 conflicts
0x19cb5847…c923
0x34b655…2a6f
2 touches
0 conflicts
0x1c86edf1…7b6d
0x34b655…2a6f
2 touches
0 conflicts
0x204dde4a…8c6d
0x34b655…2a6f
2 touches
0 conflicts
0x23253ea8…e0a4
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