pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,181,565
← previous block
next block →
recent activity
Analyzing
Block #86,181,565
11 transactions · 9 stateful · 2026-07-07 11:16:29 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
#86,181,565
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
· blocks 1
#2
execOrders
#3
execOrders
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
batchUpdate
#7
forward
#8
0x6a4ce085
#9
setData
#10
execOrders
#1
undelegate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
0
w0
1
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09000000…0007
0x000000…1000
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x0a000000…0000
0x000000…1000
2 touches
0 conflicts
0x0a000000…0001
0x000000…1000
2 touches
0 conflicts
0x0b000000…0000
0x000000…1000
2 touches
0 conflicts
0x0b000000…0001
0x000000…1000
2 touches
0 conflicts
0xb0ce5883…746c
0x2a68ba…90c5
2 touches
0 conflicts
0x29c1a140…099f
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:
Monad: Staking
1 conflict on slot
0x0900000000…000007
Audit this contract →
← previous block
·
next block →
recent activity