pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#109,229,507
← previous block
next block →
recent activity
Analyzing
Block #109,229,507
9 transactions · 9 stateful · 2026-09-30 04:42:31 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#109,229,507
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x61d59c2d
· blocks 1
#3
redeemDelegations
#4
verifyOracleProofV2
#5
execFwdPositionOpsV2
#6
0x57368ddf
#7
execFwdPositionOpsV2
#8
execOrders
#2
0x61d59c2d
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a663e9a…a9c8
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c5
0x508254…98bd
4 touches
1 conflict
0x3a663e9a…a9c4
0x508254…98bd
4 touches
1 conflict
0x00000000…0002
0x1c8a33…d316
2 touches
0 conflicts
0xa83a2a27…37a9
0x1c8a33…d316
2 touches
0 conflicts
0x3a663e9a…a9c6
0x508254…98bd
2 touches
0 conflicts
0x3a663e9a…a9c9
0x508254…98bd
2 touches
0 conflicts
0x4ea2b33b…7dbc
0x508254…98bd
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:
0x508254c8…4a98bd
1 conflict on slot
0x3a663e9a3a…2fa9c8
Audit this contract →
← previous block
·
next block →
recent activity