pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,722,558
← previous block
next block →
recent activity
Analyzing
Block #90,722,558
13 transactions · 12 stateful · 2026-07-27 08:21:11 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,722,558
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5a5d9a99
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#7
setData
#8
0x3f5c179b
#9
batchUpdate
#10
relay
#11
proposeResolution
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21ca661f…6b6a
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x023b1d10…625b
0x34b655…2a6f
2 touches
0 conflicts
0x0561b477…2557
0x34b655…2a6f
2 touches
0 conflicts
0x061b71a0…bbb3
0x34b655…2a6f
2 touches
0 conflicts
0x06f3ed5a…b2e5
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
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
0x21ca661fdd…6e6b6a
Audit this contract →
← previous block
·
next block →
recent activity