pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,849,121
← previous block
next block →
recent activity
Analyzing
Block #85,849,121
10 transactions · 9 stateful · 2026-07-05 22:18:32 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.4
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,849,121
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#4
execFwdPositionOps
#6
updateDataFeedsValuesPartial
#7
0x6a4ad8b0
#8
setData
#9
execOrders
#2
0xab083028
· blocks 1
#3
0xab083028
· blocks 1
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w2
5
w3
- 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
0x33bd5ec4…af53
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1042851b…4a31
0x065c9d…c394
2 touches
0 conflicts
0x12fa2612…3360
0x065c9d…c394
2 touches
0 conflicts
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
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