pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,810,971
← previous block
next block →
recent activity
Analyzing
Block #91,810,971
12 transactions · 10 stateful · 2026-07-31 03:39:59 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,810,971
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
execFwdPositionOps
· blocks 1
#5
forward
#6
execFwdPositionOps
· blocks 1
#8
execOrders
#9
execOrders
#10
0x6a6c1986
#11
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd3e117…3917
0x34b655…2a6f
4 touches
1 conflict
0x9efba1b3…4d54
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca8bd429…82ae
0x34b655…2a6f
4 touches
1 conflict
0x80927d7d…58a7
0x34b655…2a6f
4 touches
1 conflict
0x8cd3e117…3918
0x34b655…2a6f
4 touches
1 conflict
0x342222e8…2ec4
0x34b655…2a6f
4 touches
1 conflict
0xe84ca9a7…b041
0x34b655…2a6f
4 touches
1 conflict
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
0x8cd3e117a8…763917
Audit this contract →
← previous block
·
next block →
recent activity