pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,513,434
← previous block
next block →
recent activity
Analyzing
Block #86,513,434
8 transactions · 7 stateful · 2026-07-09 00:13:20 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,513,434
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x5a5d9a99
· blocks 2
#5
transfer
#6
depositCollateral
#7
setData
#3
0x5a5d9a99
· blocks 1
#4
0x5a5d9a99
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0x221ad076…123d
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x7c0bdc54…9dde
0x34b655…2a6f
6 touches
3 conflicts
0xa1144aa9…7f67
0x34b655…2a6f
6 touches
3 conflicts
0xb48c5e15…60a5
0x34b655…2a6f
6 touches
3 conflicts
0xedcf2991…8551
0x34b655…2a6f
6 touches
3 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: Settlement / Helper
3 conflicts on slot
0x922c7ebd9c…1c6600
Audit this contract →
← previous block
·
next block →
recent activity