pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,826,721
← previous block
next block →
recent activity
Analyzing
Block #85,826,721
12 transactions · 12 stateful · 2026-07-05 19:49:13 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,826,721
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
permit2TransferAndMulticall
· blocks 1
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
#6
forward
#7
0x8b80a919
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
0xc7e3ec2c
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xbad70b7f…57a5
0x065c9d…c394
2 touches
0 conflicts
0xc4416f2d…9c0d
0x065c9d…c394
2 touches
0 conflicts
0xf49c257c…ee45
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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:
0x04fdeac2…f747d7
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity