pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,446,047
← previous block
next block →
recent activity
Analyzing
Block #86,446,047
13 transactions · 9 stateful · 2026-07-08 16:42:59 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,446,047
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
permit2TransferAndMulticall
#4
0x5a5d9a99
· blocks 1
#5
0xed82b078
#6
execFwdPositionOps
#8
setData
#9
0xe00062…2bd5
#10
execOrders
#11
0x5d2fd812
#12
0xc7e3ec2c
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bf5914f…c75d
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x4d8766fd…f1c6
0x000000…012a
2 touches
0 conflicts
0x057ac2ab…400e
0x188d58…ea8e
2 touches
0 conflicts
0x057ac2ab…4010
0x188d58…ea8e
2 touches
0 conflicts
0x12530975…a089
0x3bd359…433a
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
0x2bf5914fac…c4c75d
Audit this contract →
← previous block
·
next block →
recent activity