pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,388,687
← previous block
next block →
recent activity
Analyzing
Block #86,388,687
12 transactions · 11 stateful · 2026-07-08 10:19:55 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,388,687
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x1a945f9c
#3
0x0f6795d9
#4
0x0f6795d9
#5
forward
#6
0x0f6795d9
#7
0x0f6795d9
· blocks 1
#8
0x6a4e24c3
#9
setData
#11
0x39435dac
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0151e996…c040
0x34b655…2a6f
4 touches
1 conflict
0x080ec687…da80
0x34b655…2a6f
2 touches
0 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x8a7af3fd…72a7
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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
0x4681609fd4…e96493
Audit this contract →
← previous block
·
next block →
recent activity