pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,463,372
← previous block
next block →
recent activity
Analyzing
Block #90,463,372
9 transactions · 9 stateful · 2026-07-26 10:37:18 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,463,372
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execPerpOps
#3
execFwdPositionOps
· blocks 1
#4
executeBatch
#6
setData
#7
execOrders
#8
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x587de2e8…162e
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf0bf41b6…682f
0x34b655…2a6f
4 touches
1 conflict
0xf3a5784b…1b60
0x34b655…2a6f
4 touches
1 conflict
0x03bf1a82…9118
0x34b655…2a6f
4 touches
1 conflict
0x03bf1a82…9119
0x34b655…2a6f
4 touches
1 conflict
0x07cfb4d8…8838
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
0x587de2e8f2…4e162e
Audit this contract →
← previous block
·
next block →
recent activity