pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,397,645
← previous block
next block →
recent activity
Analyzing
Block #91,397,645
12 transactions · 11 stateful · 2026-07-29 16:59:25 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,397,645
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x29eed2d3
#4
execFwdPositionOps
· blocks 1
#5
0x57368ddf
#6
execFwdPositionOps
#7
batchUpdate
#9
execOrders
#10
0xd708c5d8
#11
setData
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b7ed225…c793
0x34b655…2a6f
4 touches
1 conflict
0x330df1e6…7586
0x34b655…2a6f
4 touches
1 conflict
0x4abaedb1…65b9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xb562816e…1ccd
0x34b655…2a6f
4 touches
1 conflict
0x9a13592b…ecec
0x34b655…2a6f
3 touches
1 conflict
0x0bc1af53…6c7a
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
0x5b7ed225ca…03c793
Audit this contract →
← previous block
·
next block →
recent activity