pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,133,487
← previous block
next block →
recent activity
Analyzing
Block #86,133,487
11 transactions · 10 stateful · 2026-07-07 05:55:38 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,133,487
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
repay
· blocks 1
#3
execOrders
#4
updateDataFeedsValuesPartial
#5
batchUpdate
#6
execFwdPositionOps
#7
0xed82b078
#8
setData
#10
0xc7e3ec2c
#9
permitBatchAndCall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf831072…51d5
0x80f006…d585
4 touches
1 conflict
0xaf831072…51d6
0x80f006…d585
4 touches
1 conflict
0xa8669ab5…6af7
0x754704…b603
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0x451f0c72…64f0
0x57ea24…2cec
2 touches
0 conflicts
0x61c2edff…a4df
0x57ea24…2cec
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:
0x80f00661…45d585
1 conflict on slot
0xaf831072f6…c551d5
Audit this contract →
← previous block
·
next block →
recent activity