pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,590,120
← previous block
next block →
recent activity
Analyzing
Block #80,590,120
10 transactions · 8 stateful · 2026-06-11 13:43:06 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,590,120
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x98717539
· blocks 1
#4
0x3f5c179b
#5
forward
#6
updateDataFeedsValuesPartial
#7
0x6a2abbe2
#8
setData
#9
0x32366535
#3
0x98717539
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
0x656875af…444b
0xc8689a…ee79
4 touches
1 conflict
0x511cdf65…47ab
0x34b655…2a6f
4 touches
1 conflict
0x5ad8135f…d8e6
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x9a291a56…9a9c
0x34b655…2a6f
4 touches
1 conflict
0x9b36f19f…fa5a
0x34b655…2a6f
4 touches
1 conflict
0xf9d85c59…6628
0x34b655…2a6f
4 touches
1 conflict
0xfe3d37ee…6e67
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: Settlement / Helper
1 conflict on slot
0x656875af43…a8444b
Audit this contract →
← previous block
·
next block →
recent activity