pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,222,895
← previous block
next block →
recent activity
Analyzing
Block #90,222,895
10 transactions · 10 stateful · 2026-07-25 14:12:35 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,222,895
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
execFwdPositionOps
· blocks 1
#5
0x6a64c4cb
#6
transfer
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ab86b5a…8290
0x34b655…2a6f
4 touches
1 conflict
0x588380ee…0a5c
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x04e17b28…d9ef
0x34b655…2a6f
2 touches
0 conflicts
0x04e17b28…d9f0
0x34b655…2a6f
2 touches
0 conflicts
0x0beb7088…592e
0x34b655…2a6f
2 touches
0 conflicts
0x0e22f39d…b92b
0x34b655…2a6f
2 touches
0 conflicts
0x10f18761…8e0c
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
0x3ab86b5a29…728290
Audit this contract →
← previous block
·
next block →
recent activity