pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#85,779,813
← previous block
next block →
recent activity
Analyzing
Block #85,779,813
12 transactions · 11 stateful · 2026-07-05 14:36:46 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#85,779,813
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updateDataFeedsValuesPartial
#3
batchUpdate
#4
0x342c6198
#5
forward
#6
execFwdPositionOps
#7
0x6df9e92b
· blocks 1
#9
0x6a4a6c76
#10
setData
#11
execOrders
#8
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xe6f2ae57…2026
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x431fed…d150
4 touches
1 conflict
0x00000000…0002
0x431fed…d150
4 touches
1 conflict
0x00000000…0003
0x431fed…d150
4 touches
1 conflict
0x1ccfa324…0b93
0x0a917f…7777
4 touches
1 conflict
0x44ad89ba…cf83
0x0a917f…7777
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
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:
Wrapped MON (WMON)
1 conflict on slot
0xa472d565a0…ae9fe4
Audit this contract →
← previous block
·
next block →
recent activity