pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#112,246,715
← previous block
next block →
recent activity
Analyzing
Block #112,246,715
16 transactions · 9 stateful · 2026-10-10 17:51:56 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
#112,246,715
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
0x32d01e04
#2
0x59558d29
#3
0xab083028
#4
execOrders
#5
0x5acec890
#6
0x5acec890
#7
execPerpOps
#8
execPerpOps
#9
execFwdPositionOpsV2
#10
0x84403c1b
#11
0x84403c1b
#12
0x84403c1b
#13
0x84403c1b
#14
0x699cc1…e370
#15
setData
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
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x0008ef72…a804
0x34b655…2a6f
2 touches
0 conflicts
0x2902912b…448c
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
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