pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,425,031
← previous block
next block →
recent activity
Analyzing
Block #91,425,031
8 transactions · 8 stateful · 2026-07-29 19:18:23 UTC
Parallelism
75
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,425,031
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrder
· blocks 1
#3
0x5a5d9a99
#5
execFwdPositionOps
· blocks 1
#6
setData
#4
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6459805c…615d
0x34b655…2a6f
4 touches
1 conflict
0x84b10694…d9fe
0x34b655…2a6f
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0xb71dd8e4…16ae
0x34b655…2a6f
4 touches
1 conflict
0x199944d5…ab9f
0x34b655…2a6f
2 touches
0 conflicts
0x595cbd16…dac4
0x34b655…2a6f
2 touches
0 conflicts
0x73eefb08…6ca5
0x34b655…2a6f
2 touches
0 conflicts
0x961c0cd9…0937
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
0x6459805cc4…18615d
Audit this contract →
← previous block
·
next block →
recent activity