pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,882,632
← previous block
next block →
recent activity
Analyzing
Block #86,882,632
11 transactions · 7 stateful · 2026-07-10 17:23:21 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,882,632
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0f6795d9
· blocks 1
#2
0x0f6795d9
#3
updateDataFeedsValuesPartial
#5
0x0f6795d9
#6
handleOps
#7
0xed82b078
#8
0xed82b078
#9
setData
#10
0xe45ead…ea8d
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x175df07b…9de1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2afe263…745d
0x34b655…2a6f
4 touches
1 conflict
0xe822ddee…ca34
0x34b655…2a6f
4 touches
1 conflict
0xe822ddee…ca35
0x34b655…2a6f
4 touches
1 conflict
0x2bc13458…e6d8
0x34b655…2a6f
2 touches
0 conflicts
0x2bc13458…e6d9
0x34b655…2a6f
2 touches
0 conflicts
0x2e1f5171…ad2d
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
0x175df07bfe…a09de1
Audit this contract →
← previous block
·
next block →
recent activity