pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,639,268
← previous block
next block →
recent activity
Analyzing
Block #90,639,268
10 transactions · 10 stateful · 2026-07-27 01:22:10 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,639,268
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#4
executeBatch
#5
0x57368ddf
#6
forward
#8
setData
#9
execOrders
#3
execFwdPositionOps
· blocks 1
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x152f8e3d…3da0
0x34b655…2a6f
4 touches
1 conflict
0x366748e9…1282
0x34b655…2a6f
4 touches
1 conflict
0x99e2df2d…f869
0x34b655…2a6f
4 touches
1 conflict
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0x62a3f11b…03ec
0x34b655…2a6f
4 touches
1 conflict
0x0c33bb29…c6a9
0x34b655…2a6f
2 touches
0 conflicts
0x1619c024…891b
0x34b655…2a6f
2 touches
0 conflicts
0x1fdc16cf…015e
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
0x152f8e3d7f…6b3da0
Audit this contract →
← previous block
·
next block →
recent activity