pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#88,089,699
← previous block
next block →
recent activity
Analyzing
Block #88,089,699
12 transactions · 9 stateful · 2026-07-16 07:55:52 UTC
Parallelism
83
/100
Blocked
33
%
Avg conflicts / tx
0.25
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#88,089,699
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
· blocks 1
#2
updatePrices
#3
updatePrices
#4
updatePrices
#6
0x98717539
· blocks 1
#7
updateDataFeedsValuesPartial
#8
0x0f6795d9
· blocks 1
#10
setData
#5
swap
#9
0x0f6795d9
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
6
w0
8
w0
9
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xf4a27876…b09c
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5777bd87…71bd
0x34b655…2a6f
4 touches
1 conflict
0x7d56aa74…a011
0x34b655…2a6f
4 touches
1 conflict
0xfff24a53…d300
0x754704…b603
2 touches
0 conflicts
0x00000000…003d
0xa6afd3…d132
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
0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block
·
next block →
recent activity