pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#88,351,052
← previous block
next block →
recent activity
Analyzing
Block #88,351,052
11 transactions · 11 stateful · 2026-07-17 13:04:33 UTC
Parallelism
73
/100
Blocked
18
%
Avg conflicts / tx
0.27
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,351,052
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updatePrices
#3
0x0f6795d9
· blocks 2
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0x5339c59f
#8
0x6a5a28d8
#9
setData
#4
0x0f6795d9
· blocks 1
#10
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b818135…eff8
0x34b655…2a6f
6 touches
3 conflicts
0x9e70dadd…810d
0x34b655…2a6f
4 touches
1 conflict
0x9e70dadd…810e
0x34b655…2a6f
4 touches
1 conflict
0xb578940f…8837
0x34b655…2a6f
4 touches
1 conflict
0xcbe863a2…b2dd
0x34b655…2a6f
4 touches
1 conflict
0xef5cf658…2a25
0x34b655…2a6f
4 touches
1 conflict
0x05b1b07a…7a99
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0x8b81813549…3ceff8
Audit this contract →
← previous block
·
next block →
recent activity