pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,763,942
← previous block
next block →
recent activity
Analyzing
Block #91,763,942
10 transactions · 9 stateful · 2026-07-30 23:43:23 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
#91,763,942
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x23afbff3
#2
0xab083028
#3
updatePrices
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
0x0f6795d9
· blocks 1
#8
0x0f6795d9
#9
setData
#7
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ae27b09…987e
0x34b655…2a6f
4 touches
1 conflict
0xb1dd4ba4…6937
0x34b655…2a6f
4 touches
1 conflict
0x6d955786…1327
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x1eb4e731…3719
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xc469216b…ea71
0x065c9d…c394
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
0x8ae27b0982…ff987e
Audit this contract →
← previous block
·
next block →
recent activity