pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#110,308,022
← previous block
next block →
recent activity
Analyzing
Block #110,308,022
10 transactions · 9 stateful · 2026-10-03 23:11:20 UTC
Parallelism
80
/100
Blocked
33
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#110,308,022
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x286f6b9d
· blocks 1
#4
0x5acec890
· blocks 2
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOpsV2
#9
setData
#3
0x023bd359
#5
0x928e4afa
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1dc64986…6555
0x34b655…2a6f
4 touches
1 conflict
0xebc2e0d7…958e
0x3bd359…433a
4 touches
1 conflict
0x00000000…004f
0x80c745…7210
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a568
0x188d58…ea8e
2 touches
0 conflicts
0x412b95b4…2b98
0x3bd359…433a
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0x1dc64986b7…d06555
Audit this contract →
← previous block
·
next block →
recent activity