pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,672,860
← previous block
next block →
recent activity
Analyzing
Block #89,672,860
8 transactions · 6 stateful · 2026-07-23 15:57:06 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,672,860
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#3
0x0c7abd22
#4
forward
#5
updateDataFeedsValuesPartial
#6
0x6a623a4a
#7
approve
#2
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e2bbb6…2720
0x34b655…2a6f
4 touches
1 conflict
0x74f95963…01a2
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xac4f9a52…35e4
0x34b655…2a6f
4 touches
1 conflict
0x026c9423…3e4f
0x34b655…2a6f
2 touches
0 conflicts
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x0463db49…5d05
0x34b655…2a6f
2 touches
0 conflicts
0x046740ca…4065
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
0x22e2bbb6df…ea2720
Audit this contract →
← previous block
·
next block →
recent activity