pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,561,525
← previous block
next block →
recent activity
Analyzing
Block #92,561,525
12 transactions · 11 stateful · 2026-08-02 18:34:59 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,561,525
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrder
#3
0x5acec890
#4
0x5acec890
· blocks 2
#5
updateDataFeedsValuesPartial
#8
execFwdPositionOps
#9
setData
#10
execOrders
#11
0xc7e3ec2c
#6
execFwdPositionOps
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…00c9
0x34b655…2a6f
2 touches
0 conflicts
0x151e4759…60ca
0x34b655…2a6f
2 touches
0 conflicts
0x46ee3c65…4ab8
0x34b655…2a6f
2 touches
0 conflicts
0x974db92c…149d
0x34b655…2a6f
2 touches
0 conflicts
0x9efbd42c…c1bb
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.
The bottleneck
Throughput-killer:
Perpl
1 conflict on slot
0xf1345befeb…1b5530
Audit this contract →
← previous block
·
next block →
recent activity