pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,054,550
← previous block
next block →
recent activity
Analyzing
Block #90,054,550
13 transactions · 12 stateful · 2026-07-25 00:01:03 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,054,550
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
execPerpOps
#3
execPerpOps
#4
0x5a5d9a99
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
0xe9316489
#11
setData
#12
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4eb728f…0d4e
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00cd9338…40d2
0x34b655…2a6f
2 touches
0 conflicts
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
2 touches
0 conflicts
0x453a271e…8768
0x34b655…2a6f
2 touches
0 conflicts
0x4b0906c2…1abe
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
0xd4eb728fa0…680d4e
Audit this contract →
← previous block
·
next block →
recent activity