pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,449,534
← previous block
next block →
recent activity
Analyzing
Block #90,449,534
11 transactions · 11 stateful · 2026-07-26 09:27:42 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,449,534
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute302
#2
0xab083028
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#5
claimRewards
#6
0xfc8ff304
#7
execOrders
#9
setData
#10
execOrders
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f8a591e…d99b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0035
0x01bff4…1071
2 touches
0 conflicts
0x43e6056e…3a9e
0x01bff4…1071
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x1074fdfa…ff79
0x34b655…2a6f
2 touches
0 conflicts
0x1074fdfa…ff7a
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
0x9f8a591e76…59d99b
Audit this contract →
← previous block
·
next block →
recent activity