pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,322,747
← previous block
next block →
recent activity
Analyzing
Block #90,322,747
16 transactions · 14 stateful · 2026-07-25 22:37:57 UTC
Parallelism
94
/100
Blocked
0
%
Avg conflicts / tx
0
Longest chain
1
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,322,747
· 16 txs across 1 wave · depth 1
parallel ↔ serial
wave
w0
#0
syscallReward
#1
handleOps
#2
execPerpOps
#3
execPerpOps
#4
0x5a5d9a99
#5
0x5a5d9a99
#6
updateDataFeedsValuesPartial
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
execOrders
#10
0x36f359b0
#11
transfer
#12
setData
#13
execOrders
#14
execOrders
#15
0xc7e3ec2c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
● no conflicts
every tx in this block runs in parallel
Hot storage slots
Contention
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x48d0c959…7d58
0x000000…8ba3
2 touches
0 conflicts
0x7a779d73…e8be
0x000000…a032
2 touches
0 conflicts
0xa56a84d2…0dcd
0x000000…a032
2 touches
0 conflicts
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x44d20f1a…1a1a
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.
← previous block
·
next block →
recent activity