pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,501,091
← previous block
next block →
recent activity
Analyzing
Block #86,501,091
11 transactions · 9 stateful · 2026-07-08 22:51:02 UTC
Parallelism
73
/100
Blocked
22
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,501,091
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x0f6795d9
#4
0xbf6553b0
· blocks 2
#7
0x6a4ed4ce
#8
setData
#9
0xd1da03…eac0
#10
0xc7e3ec2c
#5
0x0c72758b
· blocks 1
#6
0x0c72758b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0014
0x2f55a2…8375
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x04fdea…47d7
2 touches
0 conflicts
0x7098ad85…d389
0x2f55a2…8375
2 touches
0 conflicts
0xfa328054…2380
0x2f55a2…8375
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x409d9cb9…36a8
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:
0x2f55a2e1…f48375
3 conflicts on slot
0x0000000000…000014
Audit this contract →
← previous block
·
next block →
recent activity