pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,760,900
← previous block
next block →
recent activity
Analyzing
Block #80,760,900
11 transactions · 9 stateful · 2026-06-12 08:42:14 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,760,900
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x98717539
· blocks 1
#4
0x0f6795d9
#5
executeBatch
#6
0x39abec6b
#7
0x6a2bc6de
#8
0xdf1ec6…7dc9
#9
setData
#10
0xc7e3ec2c
#3
0x0f6795d9
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
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00a4f539…8b4a
0x34b655…2a6f
2 touches
0 conflicts
0x0bfd53c0…dee0
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x4139c1b0…7457
0x34b655…2a6f
2 touches
0 conflicts
0x4fe65078…76b9
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
0xf1345befeb…1b5530
Audit this contract →
← previous block
·
next block →
recent activity