pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#86,830,798
← previous block
next block →
recent activity
Analyzing
Block #86,830,798
13 transactions · 7 stateful · 2026-07-10 11:36:42 UTC
Parallelism
85
/100
Blocked
14
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,830,798
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
0x000000b2
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
forward
#7
0x39435dac
#8
0x6a50d9c2
#9
setData
#10
0x856341…cd28
#11
0xe18800…f10b
#12
0x28486c…e724
#5
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcaf5a5ac…09f0
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00873542…6db6
0x34b655…2a6f
2 touches
0 conflicts
0x0ee13be7…7b2c
0x34b655…2a6f
2 touches
0 conflicts
0x1f374f13…2a9c
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d8
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d9
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
0xcaf5a5ac3b…8009f0
Audit this contract →
← previous block
·
next block →
recent activity