pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,066,687
← previous block
next block →
recent activity
Analyzing
Block #90,066,687
11 transactions · 11 stateful · 2026-07-25 01:02:47 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,066,687
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0xab083028
#3
permit2TransferAndMulticall
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
execOrders
#9
0xc7e3ec2c
#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
0xfef0ce0a…aa7f
0x34b655…2a6f
4 touches
1 conflict
0x0aa5e418…5d1d
0x34b655…2a6f
4 touches
1 conflict
0x2dec0e73…3189
0x34b655…2a6f
4 touches
1 conflict
0x45ea7a97…bbb3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x51d57f9a…974c
0x34b655…2a6f
3 touches
1 conflict
0x82e54444…c3da
0x34b655…2a6f
3 touches
1 conflict
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
0xfef0ce0aa8…efaa7f
Audit this contract →
← previous block
·
next block →
recent activity