pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#84,002,795
← previous block
next block →
recent activity
Analyzing
Block #84,002,795
11 transactions · 8 stateful · 2026-06-27 09:12:46 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
#84,002,795
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#3
updateDataFeedsValuesPartial
#4
exactInputSingle
#5
execFwdPositionOps
#6
0xed82b078
#7
execFwdPositionOps
#8
setData
#9
execOrders
· blocks 1
#2
0xab083028
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec94ace8…8db1
0x34b655…2a6f
4 touches
1 conflict
0xfd5ef2cf…02ae
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x5eeea918…8147
0x34b655…2a6f
4 touches
1 conflict
0x6ac6d1bf…8b19
0x34b655…2a6f
4 touches
1 conflict
0x79e62da8…efdc
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xec94ace855…818db1
Audit this contract →
← previous block
·
next block →
recent activity