pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#105,618,726
← previous block
next block →
recent activity
Analyzing
Block #105,618,726
17 transactions · 12 stateful · 2026-09-17 13:35:36 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
#105,618,726
· 17 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
execOrders
#2
0x4297b034
#3
0xab083028
#4
0x5acec890
#5
0x59558d29
#6
execPerpOps
#7
execPerpOps
#8
execPerpOps
#9
execPerpOps
#10
execFwdPositionOpsV2
#11
0x57368ddf
#12
execFwdPositionOpsV2
#13
setData
#14
0x1f6c92…cf56
#15
execOrders
#16
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
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x213b816c…a5e0
0x34b655…2a6f
2 touches
0 conflicts
0x4f3cc09a…2804
0x34b655…2a6f
2 touches
0 conflicts
0x51fc8795…1266
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