pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,291,501
← previous block
next block →
recent activity
Analyzing
Block #90,291,501
11 transactions · 10 stateful · 2026-07-25 19:59:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,291,501
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
0x6a651600
#8
setData
#9
depositTo
#10
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb944ef48…7cb7
0x34b655…2a6f
4 touches
1 conflict
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x09396f14…669f
0x34b655…2a6f
2 touches
0 conflicts
0x09a168cc…dcc0
0x34b655…2a6f
2 touches
0 conflicts
0x0a6ba3b4…2123
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
0xb944ef484a…9a7cb7
Audit this contract →
← previous block
·
next block →
recent activity