pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#80,270,801
← previous block
next block →
recent activity
Analyzing
Block #80,270,801
12 transactions · 10 stateful · 2026-06-10 02:14:10 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,270,801
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
executePacked
· blocks 2
#4
forward
#5
0x98717539
#6
0x98717539
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
executeBatch
#10
0x0c7abd22
#11
setData
#2
0xab083028
· blocks 1
#3
0xab083028
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x3c5df659…ad0c
0x065c9d…c394
2 touches
0 conflicts
0xc5c4c1d1…2145
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0003
0x5e60bc…fe22
2 touches
0 conflicts
0x00000000…0004
0x5e60bc…fe22
2 touches
0 conflicts
0x00000000…0005
0x5e60bc…fe22
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity