pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,582,134
← previous block
next block →
recent activity
Analyzing
Block #85,582,134
11 transactions · 9 stateful · 2026-07-04 16:39:20 UTC
Parallelism
73
/100
Blocked
33
%
Avg conflicts / tx
0.36
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,582,134
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execute
#2
0xab083028
· blocks 2
#4
0xab083028
#6
0x5a5d9a99
#7
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#3
0xab083028
· blocks 2
#5
0x6ad2e98b
#8
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
8
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
0x202c03eb…cf33
0xa6afd3…d132
4 touches
1 conflict
0xdec5bfea…d17f
0xa6afd3…d132
4 touches
1 conflict
0x5a30ccdd…c908
0xa6afd3…d132
3 touches
1 conflict
0x8c3a02c9…e37b
0xa6afd3…d132
3 touches
1 conflict
0xb085cc9f…3fc1
0x40c49f…2af0
2 touches
0 conflicts
0xe7a52243…fbef
0x40c49f…2af0
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