pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,798,180
← previous block
next block →
recent activity
Analyzing
Block #90,798,180
14 transactions · 10 stateful · 2026-07-27 14:41:37 UTC
Parallelism
86
/100
Blocked
20
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,798,180
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xab083028
#3
updatePrices
· blocks 1
#4
updatePrices
#5
updatePrices
#7
0x5a5d9a99
#8
0x0f6795d9
· blocks 1
#10
updateDataFeedsValuesPartial
#11
forward
#12
0x6a676e99
#13
setData
#6
updatePrices
#9
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b93487c…1992
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x152e595b…97f4
0x065c9d…c394
2 touches
0 conflicts
0x3021a222…32f5
0x065c9d…c394
2 touches
0 conflicts
0x4b86c019…9c08
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
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
0x9b93487c51…ae1992
Audit this contract →
← previous block
·
next block →
recent activity