pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,542,377
← previous block
next block →
recent activity
Analyzing
Block #89,542,377
9 transactions · 9 stateful · 2026-07-23 01:51:14 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,542,377
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updatePrices
#3
updateDataFeedsValuesPartial
#4
0x0f6795d9
· blocks 2
#5
0x0f6795d9
#7
setData
#6
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
4 touches
1 conflict
0xfc2b48cc…15e4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0a7bbfd8…ebde
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x3f4f9f22…8ad7
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x4abfb389…18f4
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
0x861e5aeffa…5cd32c
Audit this contract →
← previous block
·
next block →
recent activity