pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#80,164,316
← previous block
next block →
recent activity
Analyzing
Block #80,164,316
27 transactions · 18 stateful · 2026-06-09 14:24:03 UTC
Parallelism
85
/100
Blocked
44
%
Avg conflicts / tx
0.41
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#80,164,316
· 27 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x6a28227a
· blocks 2
#4
0xab083028
· blocks 3
#7
0xed82b078
· blocks 1
#9
0x6a28227a
#10
0x6a28227a
#11
0x98717539
· blocks 1
#14
execFwdPositionOps
#16
0x3f5c179b
#17
updateDataFeedsValuesPartial
#18
updateDataFeedsValuesPartial
#19
0x6a28227a
#20
setData
#21
0x8c4105…0c84
#22
0x9af727…1359
#23
0x4c9c63…eea0
#24
0x3d8eab…4e91
#25
0xbb2d17…484c
#26
execOrders
#2
0x6a28227a
· blocks 1
#5
0xab083028
· blocks 2
#8
0xed82b078
#12
0x98717539
#3
0x6a28227a
#6
0xab083028
· blocks 1
#13
0x3f5c179b
#15
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
4
w0
5
w1
6
w2
7
w0
8
w1
11
w0
12
w1
13
w2
15
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xdf708ee7…1fcf
0xc8689a…ee79
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
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:
Kuru Exchange: MarginAccount
3 conflicts on slot
0x13a54fa2d3…a35ae3
Audit this contract →
← previous block
·
next block →
recent activity