pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,824,528
← previous block
next block →
recent activity
Analyzing
Block #80,824,528
11 transactions · 10 stateful · 2026-06-12 15:46:32 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,824,528
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execOrders
· blocks 1
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0x57368ddf
#8
0x6a2c2a4f
#9
setData
#10
0xc7e3ec2c
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0xf6476f21…3580
0x34b655…2a6f
4 touches
1 conflict
0x37b10c3b…8fcf
0x34b655…2a6f
4 touches
1 conflict
0x548145a9…cfce
0x34b655…2a6f
4 touches
1 conflict
0x69813bdd…c3a0
0x34b655…2a6f
4 touches
1 conflict
0x9c4bf061…1101
0x34b655…2a6f
4 touches
1 conflict
0x4b6fb1f8…f5d9
0x40c49f…2af0
2 touches
0 conflicts
0x817d59fa…db13
0x40c49f…2af0
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
0xe732567db9…26b65d
Audit this contract →
← previous block
·
next block →
recent activity