pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#86,735,118
← previous block
next block →
recent activity
Analyzing
Block #86,735,118
10 transactions · 8 stateful · 2026-07-10 00:57:18 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#86,735,118
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x938bf18e
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 1
#6
setData
#7
0x1d00f0…5f06
#8
0xe16646…345d
#9
0x39435dac
#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
0x16649a8b…40b1
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x04fdea…47d7
2 touches
0 conflicts
0x00000000…0000
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0001
0x354d92…66fb
2 touches
0 conflicts
0x00000000…0005
0x354d92…66fb
2 touches
0 conflicts
0x38b5b2ce…c5bb
0x354d92…66fb
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
0x16649a8b99…4540b1
Audit this contract →
← previous block
·
next block →
recent activity