pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,750,032
← previous block
next block →
recent activity
Analyzing
Block #89,750,032
10 transactions · 8 stateful · 2026-07-23 22:26:53 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
#89,750,032
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
0x000000b2
#5
0x0f6795d9
· blocks 1
#7
0x3f5c179b
#8
setData
#9
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x27a78688…b891
0x34b655…2a6f
2 touches
0 conflicts
0x2a296f2d…2630
0x34b655…2a6f
2 touches
0 conflicts
0x2afe51f4…4006
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x737acb7813…fafce8
Audit this contract →
← previous block
·
next block →
recent activity