pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,709,195
← previous block
next block →
recent activity
Analyzing
Block #89,709,195
10 transactions · 10 stateful · 2026-07-23 19:00:36 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,709,195
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#2
execFwdPositionOps
#5
bet
#6
0x36f359b0
#7
0x6a62654c
#8
setData
#9
execOrders
#3
execFwdPositionOps
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09500602…94ea
0x34b655…2a6f
2 touches
0 conflicts
0x0b87c899…c0f9
0x34b655…2a6f
2 touches
0 conflicts
0x0d580b00…29ac
0x34b655…2a6f
2 touches
0 conflicts
0x0f2d78b1…7363
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
0x81561f70ba…26fefd
Audit this contract →
← previous block
·
next block →
recent activity