pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,852,660
← previous block
next block →
recent activity
Analyzing
Block #89,852,660
11 transactions · 9 stateful · 2026-07-24 07:04:44 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
#89,852,660
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x5a5d9a99
#3
exactInputSingle
#5
execFwdPositionOps
#6
forward
#7
updateDataFeedsValuesPartial
#8
0x6a630f04
#9
setData
#10
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0d45ffd…89cf
0x34b655…2a6f
4 touches
1 conflict
0x465ce74f…39c8
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
0x34b655…2a6f
2 touches
0 conflicts
0x495f2eb1…7b0a
0x34b655…2a6f
2 touches
0 conflicts
0x4f858307…7642
0x34b655…2a6f
2 touches
0 conflicts
0x52f7c71c…d0a6
0x34b655…2a6f
2 touches
0 conflicts
0x66a40782…f16e
0x34b655…2a6f
2 touches
0 conflicts
0x66d5e476…8a1f
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:
Perpl
1 conflict on slot
0xf0d45ffdb0…4089cf
Audit this contract →
← previous block
·
next block →
recent activity