pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,789,057
← previous block
next block →
recent activity
Analyzing
Block #86,789,057
10 transactions · 10 stateful · 2026-07-10 06:57:36 UTC
Parallelism
80
/100
Blocked
10
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,789,057
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x0f6795d9
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#7
0x57368ddf
#8
0x6a509857
#9
setData
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x698e3c53…a4c4
0x34b655…2a6f
4 touches
1 conflict
0xd6ae2f3b…8ef4
0x34b655…2a6f
4 touches
1 conflict
0xef7cdebf…b33b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x015c6c43…fa58
0x34b655…2a6f
2 touches
0 conflicts
0x015c6c43…fa59
0x34b655…2a6f
2 touches
0 conflicts
0x149ea1fb…e34a
0x34b655…2a6f
2 touches
0 conflicts
0x18091522…a560
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x698e3c537a…0da4c4
Audit this contract →
← previous block
·
next block →
recent activity