pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,907,603
← previous block
next block →
recent activity
Analyzing
Block #86,907,603
9 transactions · 8 stateful · 2026-07-10 20:10:17 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,907,603
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x0f6795d9
· blocks 1
#7
setData
#8
0x2de74c…977e
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0xaf34ae1c…04db
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f479
0x34b655…2a6f
4 touches
1 conflict
0xa2ea76a0…a726
0x34b655…2a6f
4 touches
1 conflict
0x6fea744b…029d
0x34b655…2a6f
4 touches
1 conflict
0x636446ac…f478
0x34b655…2a6f
4 touches
1 conflict
0x0e456724…6e0c
0x34b655…2a6f
3 touches
1 conflict
0x9a291a56…9a9c
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
0x671703d00b…5094b1
Audit this contract →
← previous block
·
next block →
recent activity