pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,445,286
← previous block
next block →
recent activity
Analyzing
Block #92,445,286
9 transactions · 9 stateful · 2026-08-02 08:50:21 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,445,286
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
updateDataFeedsValuesPartial
#3
0x0f6795d9
· blocks 1
#5
0x0f6795d9
#6
0xaf47a8bb
#7
0x6a6f0544
#8
setData
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbdc80bf7…e947
0x34b655…2a6f
4 touches
1 conflict
0x02d79f72…b18e
0x34b655…2a6f
2 touches
0 conflicts
0x04994ed2…9032
0x34b655…2a6f
2 touches
0 conflicts
0x19fb7d60…da48
0x34b655…2a6f
2 touches
0 conflicts
0x30c32b80…eadc
0x34b655…2a6f
2 touches
0 conflicts
0x38a6ef6a…4fee
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity