pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,755,344
← previous block
next block →
recent activity
Analyzing
Block #92,755,344
11 transactions · 11 stateful · 2026-08-03 10:50:58 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
#92,755,344
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
updatePrices
#3
execFwdPositionOps
· blocks 1
#5
updateDataFeedsValuesPartial
#6
0x8b80a919
#7
0x6a707309
#8
setData
#9
0x59558d29
#10
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x708f4f51…40e8
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
2 touches
0 conflicts
0x70a53d84…2d91
0x754704…b603
2 touches
0 conflicts
0xa949d556…184c
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:
Perpl
1 conflict on slot
0x708f4f5118…5440e8
Audit this contract →
← previous block
·
next block →
recent activity