pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,826,727
← previous block
next block →
recent activity
Analyzing
Block #85,826,727
11 transactions · 8 stateful · 2026-07-05 19:49:15 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,826,727
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
permit2TransferAndMulticall
· blocks 1
#3
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
setData
#8
0x051ce4…49d1
#9
0xbbdc7d…3792
#10
0xc7e3ec2c
#4
handleOps
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x997ccc40…4dfd
0x3bd359…433a
4 touches
1 conflict
0x13477596…b14c
0x754704…b603
4 touches
1 conflict
0x69c8bf4a…2ed0
0x754704…b603
4 touches
1 conflict
0x6d525720…f6df
0x95959a…799f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc35b1c…298f
4 touches
1 conflict
0x00000000…000a
0xc35b1c…298f
4 touches
1 conflict
0x00000000…0003
0x04fdea…47d7
4 touches
1 conflict
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:
Wrapped MON (WMON)
1 conflict on slot
0x997ccc40ce…804dfd
Audit this contract →
← previous block
·
next block →
recent activity