pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,286,725
← previous block
next block →
recent activity
Analyzing
Block #102,286,725
13 transactions · 12 stateful · 2026-09-05 21:05:13 UTC
Parallelism
92
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,286,725
· 13 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x6df9e92b
#2
execOrder
#3
execOrders
#4
0x5acec890
#5
0x5acec890
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#9
setData
#10
execFwdPositionOpsV2
#11
0x6a9c840d
#12
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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
2 touches
0 conflicts
0x81a7ba4d…8c4b
0x23c26b…7777
2 touches
0 conflicts
0x0b3eb43a…ca08
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
2 touches
0 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
2 touches
0 conflicts
0x3f5831e5…02b2
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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