pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,234,659
← previous block
next block →
recent activity
Analyzing
Block #80,234,659
11 transactions · 6 stateful · 2026-06-09 22:13:19 UTC
Parallelism
73
/100
Blocked
50
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,234,659
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#4
updateDataFeedsValuesPartial
#6
0xccf50a51
#7
setData
#8
0xcbf697…e489
#9
0xacf235…754a
#10
0x645636…f5d7
#2
0x0c7abd22
#3
0x719d975a
· blocks 1
#5
0xccf50a51
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f1434d4…1ce1
0x11ed3b…2c96
6 touches
3 conflicts
0x00000000…0002
0x2d59fc…cd50
6 touches
3 conflicts
0x00000000…0000
0x2d59fc…cd50
6 touches
3 conflicts
0x3f1434d4…1ce1
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0004
0x2d59fc…cd50
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
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:
0x11ed3b12…842c96
3 conflicts on slot
0x3f1434d4b2…9e1ce1
Audit this contract →
← previous block
·
next block →
recent activity