pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,365,653
← previous block
next block →
recent activity
Analyzing
Block #86,365,653
11 transactions · 10 stateful · 2026-07-08 07:45:42 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,365,653
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6ad2e98b
· blocks 2
#2
swap
#3
addLiquidity
#6
updateDataFeedsValuesPartial
#7
0x6a4e009e
#8
cancel
#9
setData
#10
execOrders
#4
0x3f5c179b
· blocks 1
#5
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a84c2f2…892e
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x99ecae25…abb9
0x851145…3f07
4 touches
1 conflict
0xb08bc3c2…116f
0x851145…3f07
4 touches
1 conflict
0xab791f42…61f8
0x188d58…ea8e
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
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:
0x851145ea…9f3f07
3 conflicts on slot
0x3a84c2f2fd…7a892e
Audit this contract →
← previous block
·
next block →
recent activity