pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,702,616
← previous block
next block →
recent activity
Analyzing
Block #89,702,616
13 transactions · 8 stateful · 2026-07-23 18:27:25 UTC
Parallelism
85
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,702,616
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
#2
0xab083028
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#5
0x62be7533
#7
execOrders
#8
execOrders
#9
execOrders
#10
0x6a625d85
#11
setData
#12
0x32366535
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xe8b6e4c2…e20a
0x188d58…ea8e
2 touches
0 conflicts
0xe8b6e4c2…e20c
0x188d58…ea8e
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x40e2d65d…2a35
0x3bd359…433a
2 touches
0 conflicts
0x44ed742f…63f5
0x3bd359…433a
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity