pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,829,616
← previous block
next block →
recent activity
Analyzing
Block #89,829,616
10 transactions · 9 stateful · 2026-07-24 05:08:32 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,829,616
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
execFwdPositionOps
#4
handleOps
#5
0x36f359b0
#6
0x6a62f3c8
#7
transfer
#8
setData
#9
execOrders
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89f9a9c7…7b63
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb064a9d2…a1a9
0x34b655…2a6f
4 touches
1 conflict
0x981fed49…6c9c
0x34b655…2a6f
4 touches
1 conflict
0x48b58394…2894
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x51ed538f…f725
0x34b655…2a6f
2 touches
0 conflicts
0x52e88fc2…bbcf
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
0x89f9a9c717…a97b63
Audit this contract →
← previous block
·
next block →
recent activity