pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,722,238
← previous block
next block →
recent activity
Analyzing
Block #90,722,238
11 transactions · 9 stateful · 2026-07-27 08:19:34 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,722,238
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a67150e
#8
setData
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x087cd1b0…0858
0x34b655…2a6f
2 touches
0 conflicts
0x096e297f…64b4
0x34b655…2a6f
2 touches
0 conflicts
0x1920bf9d…a626
0x34b655…2a6f
2 touches
0 conflicts
0x1c6b666d…4943
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
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
0x9a36cb2e52…470929
Audit this contract →
← previous block
·
next block →
recent activity