pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,752,813
← previous block
next block →
recent activity
Analyzing
Block #89,752,813
10 transactions · 9 stateful · 2026-07-23 22:40:55 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,752,813
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x50a0b275
#2
0xab083028
#3
0x5a5d9a99
#4
0x5a5d9a99
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
#7
0x39435dac
· blocks 1
#8
setData
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc948dbdc…199a
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe8b6e4c2…e20a
0x188d58…ea8e
2 touches
0 conflicts
0xe8b6e4c2…e20b
0x188d58…ea8e
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x5cc231f5…f1cd
0x2b46c0…1669
2 touches
0 conflicts
0x40e2d65d…2a35
0x3bd359…433a
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
0xc948dbdcb8…f4199a
Audit this contract →
← previous block
·
next block →
recent activity