pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,102,866
← previous block
next block →
recent activity
Analyzing
Block #80,102,866
11 transactions · 9 stateful · 2026-06-09 07:34:45 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
#80,102,866
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
redeemDelegations
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x98717539
#6
0xbf82f22b
#7
approve
#8
execOrders
· blocks 1
#9
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x142de65e…87ed
0x34b655…2a6f
4 touches
1 conflict
0xc166a323…1f33
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22f2d96c…f7bd
0x754704…b603
2 touches
0 conflicts
0x8bab8e89…fd2f
0x754704…b603
2 touches
0 conflicts
0xe8d3f110…9777
0x754704…b603
2 touches
0 conflicts
0x00000000…0000
0x8cd835…fab8
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
0x033cf007c8…d2136d
Audit this contract →
← previous block
·
next block →
recent activity