pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#107,444,141
← previous block
next block →
recent activity
Analyzing
Block #107,444,141
11 transactions · 11 stateful · 2026-09-23 22:47:01 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#107,444,141
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0x3f5c179b
· blocks 1
#5
0xed82b078
#6
execFwdPositionOpsV2
#7
transfer
#8
setData
#10
execOrders
#9
0xc7068c7b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x174bfcac…32ce
0x40c49f…2af0
4 touches
1 conflict
0xa2a4e273…66a2
0x40c49f…2af0
4 touches
1 conflict
0x0cfb5d79…7ccb
0x2880ab…7b43
2 touches
0 conflicts
0x0cfb5d79…7ccc
0x2880ab…7b43
2 touches
0 conflicts
0x3b0abf5d…4e33
0x754704…b603
2 touches
0 conflicts
0xb4e8fc1c…0111
0x754704…b603
2 touches
0 conflicts
0xdef25d9e…b347
0x754704…b603
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:
0x40c49f17…d22af0
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity