pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,321,531
← previous block
next block →
recent activity
Analyzing
Block #90,321,531
9 transactions · 9 stateful · 2026-07-25 22:31:47 UTC
Parallelism
67
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,321,531
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#3
executeBatch
#4
execFwdPositionOps
#6
execOrders
#7
execOrders
#8
0xc7e3ec2c
#2
0x5a5d9a99
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x0b82a929…9a58
0x34b655…2a6f
2 touches
0 conflicts
0x24933e74…db08
0x34b655…2a6f
2 touches
0 conflicts
0x27b96981…ef48
0x34b655…2a6f
2 touches
0 conflicts
0x3cf9e32f…0f64
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
0x2fd12b6c73…8702cc
Audit this contract →
← previous block
·
next block →
recent activity